GoDoc: package letsencrypt

I just recently used lego for dns based issuance, and it was excellent.

The developers working on the crypto/acme extension also wrote a stand-alone client: https://www.github.com/google/acme.

Very easy to use, can only recommend it!

I've been hosting my website using the https://github.com/diafygi/acme-tiny Python script running along with Nginx on a Raspberry Pi 1 Model B with reverse-proxy caching provided by CloudFlare from my home line for several months now. I have repo where I detail the setup and provide some config files and scripts.

I've been thinking about posting about it to HN but have not submitted it because

(a) Some of it might still be incomplete. Even though my website works perfectly, I don't remember if I've recorded absolutely everything that is needed or not.

(b) I have written a script to obtain the WAN IP from our router rather than using a 3rd party service. This is great for me because it means one less thing to worry about, but it also means that for others who are using different routers, their setup will require adjustments.

(c) Getting any attention on HN is hard. Submitted posts are most likely to gain a few couple upvotes before they quickly drown in the masses.

Anyway, since we were on the subject of other tools to use for Let's Encrypt, I figured I'd bring up acme-tiny, and when I had done so, I might as well mention all of the rest I said above.

Here's my write-up and related files: https://github.com/eriknstr/interweb

We typically run go's built-in server behind nginx. There's no need for something like gunicorn in go.

I'm running a bare Go server behind CloudFlare.

no reason imho..the function is pretty trivial. But also not a reason not to use it as a performance impact would be minimal :-)

`defer` mostly makes sense when there's multiple exit paths (returns) or if there's a chance any of the code panics. Neither is the case in this instance, so just doing it like that is fine. There is also a slight overhead for deferring, as it needs to allocate some memory on the heap

Your application likely uses more routes, and has other real work to do that won't be as brief as the example. However, the examples do work for me, and seem like a great place to start building up from.