DEV Community 👩‍💻👨‍💻

Discussion on: Goodbye Nginx, hello Caddy

Collapse
krtobias profile image
Tobias Krause

"in so many cases"
Example?

Collapse
hi_artem profile image
Artem

As mentioned, files server and proxy due to minimum configuration. Bootstraping with Caddy is easier, since it is just less steps to get going. Automation is easier and more reliable.

Thread Thread
alexgalkin profile image
Alex Galkin

Can you please clarify "more reliable" statement? Do you have some stats that may proof that? Any benchmarks that highlight benefits of Caddy vs Ngnix?

Thread Thread
hi_artem profile image
Artem

Sure. Fore example, with Caddy acme challenge for let's encrypt is built in. No need to write shell or provisioner (ansible, cheff, etc) scripts to handle this part. Less parts to fail, thus more reliable when automating.

Collapse
masroore profile image
Max Ehsan • Edited on

I'm using caddy as the development server for PHP projects. No need to install anything and create virtual hosts for multiple projects. Just unpack the binary, and copy the config file - and you're good to go. For apache/nginx, I have to create a separate vhost for every new project. With caddy I just copy a 5/6 lines long simple config file to a new project and start working immediately. (I run caddy from the terminal of course)

However, for production hosting I will go with nginx any day.

Some comments have been hidden by the post's author - find out more