3 ms·

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 dependenc

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.

isodev 3y ago
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!
- berkes 3y ago
  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.
  - campbel 3y ago
    If you mean running caddy on the same VM / server as the upstream, I suspect you're only incurring nanoseconds of extra latency.
  - ilyt 3y ago
    Well if you never build anything that does gigabits of traffic yeah, doesn't matter how slow it is