Automatic HTTPS may be the most recognized feature of Caddy but there are more that make it worth to give it a spin. Configuration simplicity is important. For

Automatic HTTPS may be the most recognized feature of Caddy but there are more that make it worth to give it a spin. Configuration simplicity is important. For example try to properly setup a reverse proxy to jenkins from nginx. Almost impossible unless you google and find the specific nginx snippet on jenkins' documentation. Deviate and you will have jenkins complaining for an improperly configured proxy. On Caddy the same can be achieved in one line with just two words (and a slash). The last feature I used for a project, was Caddy's browse directive which lets you browse files in a directory (unless there is an index.html). Not only it has a great look from the start, not only it can be templated, but also Caddy will be happy to serve you the contents of the directory as JSON. So now, not only humans but also software can browse your files easily. Have a look at its modules to get some ideas: https://caddyserver.com/docs https://caddyserver.com/docs Also go makes it easy to write a module of your own or alter one of the existing ones to fit your needs.