I currently use docker-compose to manage a number of containers, and I’ve been using traefik as a reverse proxy and to interface with letsencrypt for management of SSH keys.
However, I’ve also been reading a bit about caddy, which seems like an easier alternative to traefik, in the sense of its handling wildcard certificates. All my containers have a public facing url, like this:
which I would have thought would be tailor-made for caddy. However, in my rough searches I haven’t found out quite how to set up caddy to do this. I’ve also read (can’t remember where) that this use of caddy is ok for homelab, but shouldn’t be used for public facing sites.
So I just need a bit of advice - should I indeed switch to caddy, and if so, how? (All I need is a few pointers to good examples.)
Or should I stay with traefik, in which case, what is the easiest setup?
(I got some help with traefik a few years ago, but I’m having a lot of trouble now extending my current config files to manage a new container.)
I’m also very far from being a sysadmin expert, I usually flail around until something works.
Thanks!!
It’s not for lack of trying, but I’ve never really been able to successfully set up redirects in Traefik or Caddy
Even asking ChatGPT for help.
I ended up having success using Nginx Proxy Manager, which has a beautiful interactive UI. Despite running from a DockerCompose /Portainer
Now… if only I could distill the entire configuration into a backup file…
It’s my limited experience that nothing is easy, really, but in my case I’m looking for a solution which (a) works, and (b) is easily extendible when I add new containers.