6 ms·
It depends on your use case a bit. I'm responsible in some way for a small pile of other people's domains; for those that I do all the hosting on, I get to have
by thaumaturgy 9y ago
It depends on your use case a bit. I'm responsible in some way for a small pile of other people's domains; for those that I do all the hosting on, I get to have SSL-by-default totally effortlessly thanks to LetsEncrypt.
I have a node that can log in to other nodes, enumerate the domains they host, and then go through the LetsEncrypt authentication process for every domain on that node, retrieve the new certificate, copy it up to that node, and kick any services that need to be kicked. It runs once a day to handle renewals, or I can run it manually any time the hosting on a node changes.
I haven't had to think about SSL for quite a while now and that's fantastic.
If you're only responsible for one or a few domains, I can see how that wouldn't seem like a big deal.