Y'all seen Caddy?
-
Y'all seen Caddy?
It's a web server with a config file the size of your pinky toe, and it automagically grabs Let's Encrypt certs. I'm a convert. I mostly skipped over the nginx hype (Apache is fine, it's fast enough, it's efficient enough, it does everything including a bunch of stuff nginx won't), but I think I'm Caddy-pilled. Setting it up was so quick, and literally a three-line config file.
-
Y'all seen Caddy?
It's a web server with a config file the size of your pinky toe, and it automagically grabs Let's Encrypt certs. I'm a convert. I mostly skipped over the nginx hype (Apache is fine, it's fast enough, it's efficient enough, it does everything including a bunch of stuff nginx won't), but I think I'm Caddy-pilled. Setting it up was so quick, and literally a three-line config file.
@swelljoe seen any pointers to a “convert from nginx to caddy” docs?
-
@swelljoe seen any pointers to a “convert from nginx to caddy” docs?
@genehack I haven't, and all two (2) of my deployments have been for a new app, but the config file for the usual use case (either proxy to an app server or serve static files) is so tiny it doesn't even matter. You just tell it the name and either the path or local port. No need to tell it to exclude .well-known for Let's Encrypt validation, it does it automatically.