Hacker News Reader

Comment by zoidb | Hacker News Reader

Caddy had been a joy for me personally coming from NGINX. I especially love the ease of adding a new site and how little config it takes. Small self plug, I recently wrote an article about some cool config examples https://jarv.org/posts/cool-caddy-config-tricks/

View on HN

For local development, I don't think nginx/apache even contend against it. The config is incredibly readable, and caddy is a single executable with no dependencies.

Also for production, it's such a joy to be able to configure a VM with a single Caddyfile (or worst case, provision the server using the Caddy REST API). I love it!

Same here.

And, having mostly worked with Rails, PHP and Python http services, the proxying webserver is hardly ever a performance issue. You can stick the slowest webserver in front of a Rails (Rack) app and still be unable to measure the latency it adds.

I've been using caddy for years and while it's slower in benchmarks, than others, I've never had the practical situation where that mattered.

If you mean running caddy on the same VM / server as the upstream, I suspect you're only incurring nanoseconds of extra latency.

Well if you never build anything that does gigabits of traffic yeah, doesn't matter how slow it is

Comparing it to nginx is a such a low bar; 9 out of 10 masochists prefer nginx over any other tool.

But I see and agree with your overall point. Caddy is like a breath of fresh air, and just as useful!

It’s funny to read this, remembering when Nginx was considered the fresh air in comparison to Apache.

It’s funny because I remember when Apache was a breath of fresh air to httpd.

Reply on news.ycombinator.com