I think this is a nice option. I gave it a try —and read the source code. :)
I opted for acmetool[1] though, which albeit much larger (and thus much more difficult to verify), is easier to use [2].<p>The more impressive option I&#x27;ve seen is caddy server [3] which sets up everything automatically. You start the server and it automatically requests certificates, serves your content (static, fcgi, proxy etc) through TLS and redirects plain traffic to SSL. You don&#x27;t even need to know what let&#x27;s encrypt or ssl is. It has a bug though, every time you start the server it requests a new certificate, so after a few restarts you will get your domain temporarily banned from let&#x27;s encrypt.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;hlandau&#x2F;acme.t" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;hlandau&#x2F;acme.t</a> or `go get github.com&#x2F;hlandau&#x2F;acme&#x2F;cmd&#x2F;acmetool`<p>[2] acmetool quickstart &amp;&amp; acmetool want example.com www.example.com<p>[3] <a href="https:&#x2F;&#x2F;github.com&#x2F;mholt&#x2F;caddy" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;mholt&#x2F;caddy</a>