Caddy config (“Caddyfile”) is super easy to configure. In some cases it can be just one line to reverse proxy something. Search for a caddyfile example and you’ll see.
Comment on Nginx Proxy Manager 2.12.4 Released with Certbot Enhancements
nucleative@lemmy.world 3 days agoI’m an old school nginx pro. So I keep using nginx for reverse proxies because it’s what I know. What does caddy have to offer (or traefik is anyone wants to jump in)? Are they just optimized for this function and more modern?
couch1potato@lemmy.dbzer0.com 3 days ago
teppa@piefed.ca 2 days ago
I've just had a lot more success using Caddy when it comes to things that require mod rewrites and stuff on Nginx. I dont know what they've done differently on the back end but the compatibility with random types of web server software seems to play nicer. Also theres Certbot integration built in which is nice.
nucleative@lemmy.world 2 days ago
Makes sense, it seems like Caddy is like a Swiss army knife and nginx is now the whole Home Depot.
A decade ago or so nginx was the swiss army knife to Apache
illusionist@lemmy.zip 2 days ago
I was also used to npm. But caddy(file) is much cleaner and nicer and less hassle. It can be more difficult to set up because you may have to learn some things as it has no ui
KarnaSubarna@lemmy.ml 2 days ago
Why not Traefik as reverse proxy?
anyhow2503@lemmy.world 2 days ago
Using Traefik outside of k8s is for masochists. Especially after configv2. Caddy is by far the easiest reverse proxy to configure and has the sanest defaults.
dethmetaljeff@lemmy.world 2 days ago
What they’re asking is why Traefik/Caddy and not nginx? Do they offer anything that nginx doesn’t? Nginx is pretty tried and true and honestly, in this space, I personally prefer tried and true over new and shiney unless new and shiney offers something I need that old faithful doesn’t.
To be fair, I was an Apache hold out for a looong time until I accepted my lord and savior nginx into my heart.
Nibodhika@lemmy.world 2 days ago
Configuration is much easier, e.g. this is the full config you need to expose nextcloud on
nextcloud.example.com(assuming caddy can reach nextcloud using the hostnamenextcloud)Comparing that to ngnix configs that need a template for each different service (although to be fair they’re mostly the same).