3 ms·

What about Caddy made it easier? It's very simple to set up a basic Nginx site and run certbot... like 'under 5 minutes' simple.

by DKnoll 9y ago

eridius 9y ago
Caddy does it all without needing an external dependency or crontab or custom configuration to handle the HTTP challenge. Caddy config files also just end up being simpler in general. When I moved from Nginx to Caddy my vhost files ended up at least 50% smaller, if not more, and with a lot less repetition. Note that when you create a new vhost in Caddy it automatically gets LE support. No need to update your crontab to pass the new domain to certbot.
- DKnoll 9y ago
  Certbot manages its own cronjobs, same with changing the config to handle the HTTP challenge. A reason not to use Caddy is significantly reduced performance as compared to Nginx.
  - eridius 9y ago
    Sure, if you’re at the point where the performance of Caddy is a limitation, by all means switch to Nginx. My sites aren’t even close to that limit though, and it’s a lot simpler to start out with Caddy. No sense in doing unnecessary work before you need to.
    - DKnoll 9y ago
      There isn't a hard limit (that I know of), you're just consuming more resources for each page load and likely doing it slower than nginx would.
      - eridius 9y ago
        By the same argument you should never use node.js or ruby or python or whatnot to write your app and should always use something like C++ or Rust.
        DKnoll 9y ago
        If you consider creating a ~10 line site config in nginx equivalent to developing an entire application in Rust... sure?
  - mholt 9y ago
    Caddy didn't break when Let's Encrypt disabled the TLS-SNI challenge. Many other ACME clients (even Certbot) did. Also, having a fully-integrated solution will be more reliable and lower-maintenance, especially in the long run. And Caddy's faster than you think -- "significantly reduced performance" is an overgeneralization. Caddy may happily serve tens of thousands of requests per second. (It all depends on, well, a lot of things.)

What about Caddy made it easier? It's very simple to set up a basic Nginx site and run certbot... like 'under 5 minutes' simple.

by DKnoll 9y ago

What about Caddy made it easier? It's very simple to set up a basic Nginx site and run certbot... like 'under 5 minutes' simple.

eridius 9y ago

Caddy does it all without needing an external dependency or crontab or custom configuration to handle the HTTP challenge. Caddy config files also just end up being simpler in general. When I moved from Nginx to Caddy my vhost files ended up at least 50% smaller, if not more, and with a lot less repetition. Note that when you create a new vhost in Caddy it automatically gets LE support. No need to update your crontab to pass the new domain to certbot.

DKnoll 9y ago
Certbot manages its own cronjobs, same with changing the config to handle the HTTP challenge. A reason not to use Caddy is significantly reduced performance as compared to Nginx.
- eridius 9y ago
  Sure, if you’re at the point where the performance of Caddy is a limitation, by all means switch to Nginx. My sites aren’t even close to that limit though, and it’s a lot simpler to start out with Caddy. No sense in doing unnecessary work before you need to.
  - DKnoll 9y ago
    There isn't a hard limit (that I know of), you're just consuming more resources for each page load and likely doing it slower than nginx would.
    - eridius 9y ago
      By the same argument you should never use node.js or ruby or python or whatnot to write your app and should always use something like C++ or Rust.
      - DKnoll 9y ago
        If you consider creating a ~10 line site config in nginx equivalent to developing an entire application in Rust... sure?
- mholt 9y ago
  Caddy didn't break when Let's Encrypt disabled the TLS-SNI challenge. Many other ACME clients (even Certbot) did. Also, having a fully-integrated solution will be more reliable and lower-maintenance, especially in the long run. And Caddy's faster than you think -- "significantly reduced performance" is an overgeneralization. Caddy may happily serve tens of thousands of requests per second. (It all depends on, well, a lot of things.)