Currently, I use dockerproxy + swag and Cloudflare for externally-facing services. I really like that I don’t have to open any ports on my router for this to work, and I don’t need to create any routes for new services. When a new service is started, I simply include a label to call swag and the subdomain & TLS cert are registered with Cloudflare. About the only complaint I have is Cloudflare’s 100MG upload limit, but I can easily work around that, and it’s not a limit I see myself hitting too often.
What’s not clear to me is what I’m missing by not using Traefik or Caddy. Currently, the only thing I don’t have in my setup is central authentication. I’m leaning towards Authentik for that, and I might look at putting it on a VPS, but that’s the only thing I have planned. Other than that, almost everything’s running on a single Beelink S12. If I had to, I could probably stand up a failover pretty quickly, though.
Haven’t messed with it personally (yet), but I’ve seen some examples where Caddy can do some cool stuff (I think the example I saw recently was defining routes that can call an arbitrary program with the HTTP request details).
I use Nginx almost exclusively (I’ve got HAProxy in the mix, too, but it’s strictly for load balancing). Everyone always keeps recommending Traefik to me, but from what I’ve seen, it doesn’t do anything Nginx can’t already do, and the config is all bizarre and way less intuitive. Not saying it’s bad, just not for me. (This is not an invitation to proselytize Traefix at me lol).
Use whatever works for you.
I guess this is what I was getting at. From what I can tell, at their core, both do pretty much what Swag is already doing for me. Was mainly curious about additional functionality I hadn’t thought of. Most of what I’ve done so far is stuff I hadn’t thought of until I saw it mentioned here, reddit, or in the linuxserver list.