As far as I can tell, there is no computer program that makes it simple and easy to self-host a website for publishing content and hosting discussions.
Not a full solution, but I have a LightSail install script that sets up a FreeBSD/Apache/MySQL/FastCGI PHP server. Post-install actions are provided in the login message.
another big gripe I have with a lot of these partly pre-configured monstrosities I have: Often they use default configurations for parts of the stacks which are really against the intended use case and often this is the reason why everything is slow and tends to break. I have seen this so many times with docker swarms, Laravel (for me this is code ebola), WordPress solutions, PHP whatever. Everything is slow, catches every resource it can get and still wants more. We are living in a world, where it is often easy to gain 10 x, 100x or even 1000x performance improvements with some brain, but brain gotten uncool, so we just throw hardware at it.
My self-hosted is simple, really. It was XAMP/LAMP/WAMP, etc. simple, ideals, and have been out for at least a decade.
Not a full solution, but I have a LightSail install script that sets up a FreeBSD/Apache/MySQL/FastCGI PHP server. Post-install actions are provided in the login message.
https://github.com/torstenvl/bamf/blob/master/setup.sh
This is antithetical to everything I said in this article.
1. It's a bash script. It requires technical knowledge
2. It expects a specific package manager to exist on the system, and uses it to install many packages
3. This is not a self contained system. This is a script that glues and configuring many separate systems to achieve the goal of serving a website.
4. Setup script is complicated. If something fails half way through, the user has no idea how to proceed.
I don't know if you read the article or if you found this because you are looking for places to share your setup script.
This is what I said in the article:
> The installation time is basically just the file upload time. The actual
> installation is nothing but creating a specific user and home directory for
> that user and giving the server program the capability to listen on ports 80
> and 443. It shouldn't take more than a fraction of a second.
>
> Nothing on the server needs to be messed with or configured. No "packages"
> need to be installed. Ever.
another big gripe I have with a lot of these partly pre-configured monstrosities I have: Often they use default configurations for parts of the stacks which are really against the intended use case and often this is the reason why everything is slow and tends to break. I have seen this so many times with docker swarms, Laravel (for me this is code ebola), WordPress solutions, PHP whatever. Everything is slow, catches every resource it can get and still wants more. We are living in a world, where it is often easy to gain 10 x, 100x or even 1000x performance improvements with some brain, but brain gotten uncool, so we just throw hardware at it.