Compared to what? You think nginx is not easy to configure or has insane defaults somehow? Really baffled why people come out of the wood work to pile on beautifully architectured designs in favor of some random project they happen to like or just because it's written in a language they have a special affinity for like Go or something.
Also, you could asked all your questions without being incendiary and making assumptions about why people like Caddy. Nobody mentioned Go except you.
nginx: https://github.com/shepherdjerred/servers/tree/8688ba2086d87...
caddy: https://github.com/shepherdjerred/servers/tree/main/zeus/con...
I have a feeling you're think we're attacking nginx. I can't speak for the other poster, but I have huge respect for nginx. It's a great piece of software and it's what I'd reach for in production.
I'm not sure that Caddy is a good choice for production, but for my hobby work it is just so much easier to use.
(And Caddy is an excellent choice for production. Or so says the many companies now powering half a million sites with it!)
certbot --nginxWhat about HTTP->HTTPS redirection, etc?
Same for secure cipher selection.
All of that Caddy gives you in 1 line of config (i.e. domain name)
If we allow your example, then caddy wins hands down because it also makes me rich because it fronts the websites that make me money.
But that would be ridiculous thing to claim Caddy does, because it doesn't do that itself.
With the announcement a couple of days ago that the commercial nginx folks are embracing OS again I might take another look.
For what its worth, I switched from nginx to Caddy years ago and haven't looked back - Caddy's built in support for LetsEncrypt and zero configuration for the most common reverse proxy scenarios is just too compelling to ignore now - the speed and ease with which one can throw up an SSL front end with valid letsencrypt cert is amazing.