I've said it before when caddy was last mentioned, but this is how I want Let's Encrypt to work with all web servers. Yes. That includes the big ones like nginx, apache and even IIS.

By default, all that's needed is to turn on ssl and you'll be up and running - including a let's encrypt certificate.

Following this vision is why I believe that let's encrypt limited the validity period of their certs (in addition to some security benefits and much lower OCSP load): Once the integration into clients has proceeded to this level where caddy is showing us it's going to, then even quicker expirations would become feasible - heck even as low as a week or so.

So, while I'm not planning on using caddy any time soon (I don't see a benefit to switching away from nginx right now), I applaud caddy for showing everyone how this should be done.

A huge thank you to the author. This goes to show how very important UX is even for backend-y stuff.