[xnaas]

I played with Caddy a lot in the v1 days and again recently with v2.1. I ended up not sticking with it since there's things I do with nginx that aren't easy to do with Caddy if you don't have extensive Go knowledge. I am tempted to give it an honest go again, though, and see what I/it can do.

As for Caddy advantages, I think it's really just about having a super easy to manage JSON or Caddyfile. In migrating a few of my nginx configs to Caddyfile, I was able to reduce line counts from dozens to 2-3. That's pretty impressive, tbh.

If you've been using nginx forever and have no issues with it...I don't see any valid reasons to move to Caddy.

[e12e]

The only out-of-box thing I sometimes miss, is "try-files-first" -- but I'll also say it probably is a bit of an anti-pattern (just have static files under another path/sub-domain - etc).

But it is something that nginx does have. That, and maybe some kind of "x-send-file" acelleration/support.

Ed: this is odd, I could've sworn it wasn't that long ago I looked for and even discussed try-files-first for v2 - but apparently it exists?

https://caddy.community/t/v2-try-file-server-first/6440/3

https://caddyserver.com/docs/caddyfile/directives/try_files#...

Ed2: I guess I was confusing it with x-send-file acelleration - which still appear to be a bit wip? :

https://caddy.community/t/caddy-2-x-sendfile-x-accel-support...

https://caddy.community/t/sendfile-x-accel-redirect-v1s-inte...