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.
ex-Technical Manager at GeeksForLess Inc. I helped partners and customers converting ongoing business challenges into technical tasks; then monitoring their execution and delivering the result.
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?
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.
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.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
"in so many cases"
Example?
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.
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?
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.
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.