7 ms·

> and tries to steer you towards, its API, confusing JSON config syntax I disagree. The docs don't do that. What you're probably talking about is the Getting S

> and tries to steer you towards, its API, confusing JSON config syntax I disagree. The docs don't do that. What you're probably talking about is the Getting Started guide https://caddyserver.com/docs/getting-started https://caddyserver.com/docs/getting-started, which is a tour of how Caddy works, so it first shows you the "bare-metal" look at how it works, then it introduces the Caddyfile which allows you to simplify your user experience. There's even a comparison table between the two https://caddyserver.com/docs/getting-started#json-vs-caddyfile https://caddyserver.com/docs/getting-started#json-vs-caddyfi... which explains when you'd want to use JSON (i.e. if you want programmable, API-based usage) or Caddyfile (i.e. for quick-and-simple hand-written config, 95% of users choose this). I recommend starting from https://caddyserver.com/docs/caddyfile-tutorial https://caddyserver.com/docs/caddyfile-tutorial or https://caddyserver.com/docs/caddyfile/concepts https://caddyserver.com/docs/caddyfile/concepts to get an idea of how the Caddyfile works.

SahAssar 3y ago
That might be true now, but I spent a lot of time trying to use caddy v2 and not being able to since the only docs where for json and some things where available in caddyfile and some in json. If it is fixed now then that is great, but it took at least a year (I'm guessing more) after the launch of v2.
- francislavoie 3y ago
  Of course it wasn't going to be perfect at the initial release, nothing ever is. Caddy v2 was a complete rewrite from v1, so there was a lot of TODOs to polish it up. Definitely take another look now, there's been a ton of progress since then, 3 years ago. The initial v2 release was in May 2020, soon after the pandemic hit.
  - SahAssar 3y ago
    > Of course it wasn't going to be perfect at the initial release, nothing ever is What I'm trying to say is that on launch v2 was not a good replacement for v1, especially in the docs area. I've seen quite a few major version bumps in OSS, and it feels docs is an area that is usually neglected, and for quite a while (at least a year, I'd say more) the v2 docs where not useful for someone who had not participated in the caddy v2 community discussions. I'm just trying to describe what led me to go from a avid caddy proponent back to an nginx user. I'll take another look next time I have a project that needs a http/s server!

SahAssar 3y ago

That might be true now, but I spent a lot of time trying to use caddy v2 and not being able to since the only docs where for json and some things where available in caddyfile and some in json. If it is fixed now then that is great, but it took at least a year (I'm guessing more) after the launch of v2.

francislavoie 3y ago
Of course it wasn't going to be perfect at the initial release, nothing ever is. Caddy v2 was a complete rewrite from v1, so there was a lot of TODOs to polish it up. Definitely take another look now, there's been a ton of progress since then, 3 years ago. The initial v2 release was in May 2020, soon after the pandemic hit.
- SahAssar 3y ago
  > Of course it wasn't going to be perfect at the initial release, nothing ever is What I'm trying to say is that on launch v2 was not a good replacement for v1, especially in the docs area. I've seen quite a few major version bumps in OSS, and it feels docs is an area that is usually neglected, and for quite a while (at least a year, I'd say more) the v2 docs where not useful for someone who had not participated in the caddy v2 community discussions. I'm just trying to describe what led me to go from a avid caddy proponent back to an nginx user. I'll take another look next time I have a project that needs a http/s server!