[stephenr]

The author (mholt) replied above and the 'district advantage' he identified for caddy, his own product was:

> Caddy is the only server, even in the face of mod_md, to have fully automatic HTTPS by default

In every discussion about Caddy I've seen, the same argument is made. Even when caddy would refuse to start (with valid certificates cached!) during the LE outage, the response was "but we do LE + TLS automatically".

I still don't understand the concept of Caddy. The project seems inherently aimed at hobbyist's at best based on the idea that "its too hard to enable TLS in $Competition", but similarly they provide literally zero support for actually running Caddy - no sysvinit script, no systemd unit file, NOTHING.

So tell me again who their target market is? People who can't enable TLS in <Apache/HAProxy/Hitch/Nginx> but can write a fucking unit file for systemd?

[JdeBP]

They've been publishing a systemd unit file, a van Smoorenburg rc script, a Mewburn rc script, a MacOS plist, and an upstart job file since 2016.

* https://github.com/mholt/caddy/tree/master/dist/init

[stephenr]

Ok, thats news to me.

However, I stand by the basic point I was making: the process to get caddy running is not just "apt install caddy-server", and it works.

It's quite possible you could spend more time getting caddy working from a download than you would enabling Certbot + TLS in a competing web server.