My collection of dockerfiles.
In most cases though, I use docker-compose files.
Every sub-folder contains the recipe for a single service or collection of services.
In docker 🐳 land, they are also called stacks.
Almost all services are centered around a reverse proxy, in my case traefik. Traefik is a really nice reverse proxy, because
- it can take car of automatic service detection in all running docker containers
- it automatically fetches new SSL certificates through Let's Encrypt
- it has a nice dashboard
Another service is portainer. It connects to the docker 🐳 daemon and allows controlling everything that is running through docker. A great place to debug or configure all others.
Most recipes are stand-alone and only require the setup of Traefik.
For this, create the few external resources by running the init.sh script.
The recommended order in which to bring up this project is:
- Run
init.shto create the external, across-stack resources. - Bring up the authentication stack
auth. - Bring up Traefik with the
traefikstack. - Bring up Portainer with the
portainerstack. - Use Portainer to bring up all the other stacks. If a local portainer dataset already existed, the entire node configuration with all stacks will still exist, too. Simply Pull & redeploy each stack.