I run it in a container without problems. All you have you do is bind it to port 80 and 443. I prefer the container to running it directly within the host OS for ease of portability.
Also strongly recommend building it with support for DNS based validation. Using DNS validation you can have multiple instances running across the different servers you ha e to easily switch to or provide better local routing. For example please. I run one caddy frontend on a VPS that routes my traffic most of the time, but when I’m at home my DNS points me at a very instance that is running on my server on my home network avoiding the path of lit to the internet and back home. Using http based validation would require me to sync certs around.
mereo@piefed.ca 1 week ago
I don’t think running Caddy in a container is needed. All my apps are docker images and Caddy is a system app. I treated as an important OS app.
JRaccoon@discuss.tchncs.de 1 week ago
Agreed