While this might be obvious to people that know Caddy well, it wasn't for me and it took me a moment to figure out how to set this up.
There are use cases in which you can't rely on labels to configure your docker setup and you have to do it statically for whatever reason (as you have maybe connected your "ghetto swarm" through a VPN or you're only using swarm to have an overlay network but you're not really using the swarm functionality to deploy services as some services don't even scale with swarms). For those scenarios I would appreciate a static.yaml or something like that in the examples.
I migrated from the image SteveLTN/https-portal and needed a similar way of handling things by defining my proxy settings on the proxy container and not through labels on other containers š
While this might be obvious to people that know Caddy well, it wasn't for me and it took me a moment to figure out how to set this up.
There are use cases in which you can't rely on labels to configure your docker setup and you have to do it statically for whatever reason (as you have maybe connected your "ghetto swarm" through a VPN or you're only using swarm to have an overlay network but you're not really using the swarm functionality to deploy services as some services don't even scale with swarms). For those scenarios I would appreciate a static.yaml or something like that in the examples.
I migrated from the image SteveLTN/https-portal and needed a similar way of handling things by defining my proxy settings on the proxy container and not through labels on other containers š
Here's my current docker-compose.yml:
Feel free to copy into the examples