I've converted several projects over to Caddy[1] and been very happy with it. Caddy is a web server with Let's Encrypt integration built in. Your config can be as simple as:<p><pre><code> example.com {
root path/to/root
}
</code></pre>
And Let's Encrypt will automatically be used. It's amazingly simple.<p>I wonder if in the future we'll see things like mod_acme that automate Let's Encrypt into other servers.<p>[1] <a href="https://caddyserver.com/" rel="nofollow">https://caddyserver.com/</a>
Shouldn't something called Acme work more like mk than make?<p>Good work and good ideas though. I haven't looked at the Python client, but it seems like there may be some valid points here.
I'm a bit confused about the "non-root support" -- the (somewhat lengthy) setup manual absolutely seems to require root to set up users and directories in the root filesystem.<p>In contrast, the official client can absolutely work without having root access. You can install it locally (pip install --user letsencrypt) and change all working directories to paths your user can write to using a configuration file.
The official let's encrypt client will happily not modify your configuration, too. I don't understand why being distributed as a binary is important.