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!!
I have several issues with traefik: first is that I can’t access the dashboard. The second is that as I was given a LOT of help setting it all up (some years ago), I’ve ended up with config files that I don’t fully understand myself. When I tried, for example, to use traefik for certificates to protect my installation of mealie, I simply couldn’t. So my mealie instance is unprotected, running just with http.
I’m getting to the stage where I’m thinking about paying for some professional sysadmin time … As I said in my OP, I’m nowhere near competent as a sysadmin, especially with networking, and if I can get something to work, I’m thrilled and never want to touch it again, in case I break it.