4 ms·
The certbot let's encrypt agent is unfortunately stuck in a Snap package, at least last I tried setting it up. Always feels like Snap has been pushed by some i
by akersten 5y ago
The certbot let's encrypt agent is unfortunately stuck in a Snap package, at least last I tried setting it up.
Always feels like Snap has been pushed by some invisible proprietary influence, not organic growth due to it being a good idea. I never saw anything wrong with package managers or a reason I should like Snap. My experience is that I've only been forced to use it against my will.
- greatgib 5y agoI was also very annoyed by that and supporting legacy servers with letsencrypt, and then I found acme.sh script to replace certbot: https://github.com/acmesh-official/acme.sh https://github.com/acmesh-official/acme.sh Simple and light without big dependencies as running in bash! I would recommend it a thousand times!
- hedora 5y agoOpenBSD started packaging an ACME client: https://man.openbsd.org/acme-client.1 https://man.openbsd.org/acme-client.1 It's probably also a reasonable alternative.
- _joel 5y agomicrok8s perhaps, oh and they use it on AWS AMI's for awscli stuff (yuk)
- throwawaymanbot 5y ago