docker-unit-alpine

And to add one more option to the comments (beyond [frontend] + php-fpm): Nginx Unit https://unit.nginx.org/ - like Apache + mod_php runs as a single service, handles the multiprocessing of php (and other languages), static files, reverse proxy and even lets you configure both itself and php via a single configuration (either as a file or dynamically at runtime, via a socket): https://unit.nginx.org/configuration/#php Here is an IRL config example: https://github.com/PrivateBin/docker-unit-alpine/blob/master... The resulting container image can be pretty small: https://hub.docker.com/r/privatebin/unit-alpine

> What is not well documented IMHO is that you don't have to load the config at runtime - if you place the JSON file in the (compile time changeable) /var/lib/unit directory it will be loaded on startup, similar to a traditional /etc config file. But it also will get updated at runtime, if configuration is uploaded on the config socket, making it persist service restarts, hence /var is more appropriate than /etc. Thank you very much for this example, and calling out the config file option. Do you find that you get any use from the config api in your setup (vs pushing a new container)? I imagine it might be more useful if nginx unit acts like a k8s ingress like setup? As for: > both webserver and php configuration are in one file[1]. That's just the line in the Docker file: COPY --chown=${UID}:${GID} conf.json /var/lib/unit/ I found the

This tool does have it's appeals to folks that run web applications behind web servers in containers. For example, in this project we use nginx + php-fpm to serve some PHP app: https://github.com/PrivateBin/docker-nginx-fpm-alpine It uses s6 to handle nginx + php-fpm services, meaning we have to maintain configuration for s6 services (written in execline), nginx webserver configuration files (nginx proprietary format) and php-fpm (INI format). I've created a fork that replaces that stack with nginx unit: https://github.com/PrivateBin/docker-unit-alpine No need for a service manager and both webserver and php configuration are in one file[1]. What is not well documented IMHO is that you don't have to load the config at runtime - if you place the JSON file in the (compile time changeable) /var/lib/unit directory it will be loaded on startup