Uses php-fpm image and is served through a simple caddy server.
Automatically deploys by default and can be automatically deployed with
smtp e-mail sending and s3 primary object storage optionally if desired.
Utilizes some necessary hackery for container ordering and startup so
startup is relatively slow (takes around 2-5 minutes at least) but once
running should be stable and uninterrupted.
Implements health-checks for all involved containers.
Switch apache for php-fpm image
Created bind volume for caddy which takes the json fragments which will
later be injected through the caddy api to dynamically set their
individual reverse proxy addresses.
This is not entirely necessary if the injection should be done as a
variable instead, but makes it easier to change routes and especially
more complicated ones (I'm thinking of gitea with ssh access e.g.).
Added caddy as swarm container. Uses templated Caddyfile which can be
set up for testing purposes for now.
Depends on docker and docker-swarm, and will keep its stuff where
docker-swarm sets itself up.
