Archiving my Twitter, Facebook and other social network activity
Every time my websites’ database server goes down, two things cross my mind:
– Would it be worth managing the server myself so I can at least troubleshoot it?
– Would it be worth migrating two decades’ worth of WordPress blog posts to a static site generator and just ditching the DB going forward?
OK, three:
– What changed that is causing the server to go down every couple of weeks instead of once a year?
In other news, #DreamHost migrated my main VPS with no hiccups as near as I can tell. I had to manually launch Agate for my #gemini capsule, but I suspect that’s only because they brought up the new system before moving the users over to it.
Here’s hoping it’s more stable than the Nginx one. I think I may just not have allocated enough RAM to the Nginx box, since the new plans don’t let me choose in-between sizes like 1.2 GB, 1.7GB etc. like the old plans did. The VPSes both ran rock solid for years, but DreamHost’s nginx support has always seemed like an afterthought.
I’m probably going to drop the Nginx VPS at some point. I just need to decide what to do with the last remaining site on it: Consolidate on the Apache VPS (possibly with more RAM), or set up a dedicated Nanode and manage it myself (and find out what resources it actually needs on a lighter-weight system)