I'm paying for two servers at aws for the time being, until I figure out if there was anything left on the old server that I can't recover. Could be I can't get anything back from it anywhere, it seems to be knackered. The only things I know are missing are files with passwords in that were not committed to the repo, one within the twitter / oauth thing I use for posting new messages here (can live without that for a while as no-one else ever posts here) and also my proxy for tweeting all of our lights going on and off and so on at @ourduino. Yeah, we can manage without that for a while too, I was thinking of shutting it down anyway.
Must have been some kind of disk corruption that first manifested itself by corrupting my database indices, hence the super slow responses, then it has spread. My processes are improved now, so I should be able to recover again quite quickly. Going to move from a spot instance to a reserved instance next too, as this blog is on 24/7.
Paul Clarke's blog - I live in Hythe in the deep South. Married + father to 2, I am a full-stack web engineer, and I do javascript / nodejs, some ruby, python, php ect ect. I like pubbing, running, eating, home automation and other diy jiggery-pokery, history, genealogy, Television, squirrels, pirates, lego, + TIME TRAVEL.