New Docker image for LinkAce v2

[Kovah]

Currently, there are two images available for LinkAce: one which only contains the application and needs a separate web server like nginx, and one that is able to run on its own as it contains said web server.

To make things easier for the users who want to set up LinkAce and me as maintainer, I want to publish only one image in the future that contains a web server. There will be only one setup process for Docker for version 2.

• [x] Remove the advanced image. linkace/linkace:simple becomes linkace/linkace and the previous linkace/linkace will be removed.
• [x] Check which web server to use in the final image, nginx and Caddy are viable options.
• [x] Publish the image on both the Docker Hub and the Github Container Registry.
• [ ] Update the docs to use the www-data user when running commands inside the container.
• [ ] Test a possible HTTPS setup with Caddy and a separate config file.

---

Edit:

• I moved from nginx to Caddy. Caddy is easier to configure and manage than nginx.
• Caddy is configured to trust all private networks as proxies, including Docker networks.
• The release Docker image is ready to be used with SQLite without difficult configurations. Only DB_CONNECTION and DB_DATABASE are needed.
• The base image now includes Supervisor and Caddy by default which saves a bit of build time.
• The ownership and permissions of the files inside the image are changed to www-data to prevent permission conflicts.

[ffraenz]

I think merging the PHP and Nginx containers is a great improvement. I never was satisfied with combining the two in my own setups. Also, having less images to maintain is long term a win for everyone.

However you should keep the existing images/tags for as long as possible to not break existing installations or automated deployments.

It would be nice having a documented integration point or strategy to configure Let's Encrypt with it as that should be an important use case.