4 ms·

From the first glance it doesn't look convincingly better than a generic and manually polished nginx configuration. Are there any other benefits to Caddy?

• corobo 2y ago
  It does all the letsencrypt stuff for you - certbot is not a massive hassle if you're just serving the one domain of course but I really liked it for that when I was setting up a redirect server (corps do love buying TheirBrand.everytld haha) Set the config up with CI/CD and can now just edit the config and git push knowing Caddy will just handle the rest
  • ac130kz 2y ago
    Seems to be a middleground between doing certs on a small scale with cronjobs and a fully fledged automated Kubernetes cluster.
    • nyolfen 2y ago
      it is a total displacement for the former and stupidly simple compared to the either; gold standard 'just works'
• 9dev 2y ago
  If you choose to start the project with docker compose, you’ll notice how it will immediately bring up a fully functional reverse proxy setup with TLS support on localhost; set the SITE_DOMAIN environment variable to your proper domain instead, and you’ll find that configured as well, along with a proper, ACME-issued certificate. Add a bit more effort, and you’ll also get mTLS for all services automatically. All of this is more or less doable with nginx, I’ve done it often enough. But read the Caddyfile and tell me this isn’t miles ahead in clarity.
• otabdeveloper4 2y ago
  Better Docker integration out of the box, I guess. I don't use docker so I don't care.