For me Let's Encrypt came out at the right time. They said they will automate the 90-day renewal process.
For me Let's Encrypt came out at the right time. They said they will automate the 90-day renewal process.
On top of that, whereas on a shared host i click a button and host a second domain, with a VPS I have to SSH in and manually edit server files.
But everyone always recommends running a VPS so I can't help but imagine I've either missed some magical tool that makes running a VPS a snap or it's just not a realistic solution for most people.
> SSH in and manually edit server files.
Docker solves almost all those problems. Comes with its own complexities, though.
But if you're configuring multiple nodes that are similar or the same you should definitely be using images. Setup one node, create an image of it, and then create new nodes from the image.
I'd also like to integrate it with https://github.com/voltagex/junkcode/blob/master/Python/spot... so I can do "least cost provisioning"
For example with haproxy you need the entire chain and private key together, which I have to do manually. As the API is open it's doable - I may even do something myself.
I can't wait until I have something that somebody else or I has written that, once the API is complete, you can stick in a cron job and does the concatenation and reloads haproxy/nginx/whatever. Until then the whole thing is beta.
It's not even the monetary aspect - i'd happily pay for certs, but LE is so on the way to making it a devop as opposed to a finance/ops thing that it needs to be encouraged. Donation incoming...
Back when I used to do frequent freelancing for the type of client who used shared hosting, I don't think I met a single one who hosted static sites, even though for many of them static would have been more appropriate and far more secure and performant.
You're probably thinking of http://lowendbox.com/