Once in a while you’ve got to pull the trigger and actually ship some code.
It’s been seven years (!!!!) since I did anything serious with the way this blog looked and worked. There were plugins that weren’t supported anymore. The old theme had been so extensively customized by me that it wasn’t upgradable, and didn’t really work well with new functionality or WordPress releases. A lot of the new functionality duplicated what I’d hacked into the theme, too. Stuff like Google +1, sharing, etc. Plus I wanted SSL (and not just CloudFlare’s poser Google juice SSL crap, I wanted the security).
I started redoing the site six months ago, where “redoing” meant the cloud-esque “completely starting over.” The synchronization of content between my development site and the live site was pretty involved, and I found myself avoiding writing because I knew it’d just be more to synchronize later. Realistically a few more posts wouldn’t have mattered much, but it became a serious mental obstacle to writing, on all fronts.
Then came some asshats, hammering the old blog’s XML-RPC interface, trying to break in.
If you’ve tried to get to this site in the last couple of weeks and it’s been down it’s because those idiots went from breakin attempt to DoS, essentially causing Apache to use too much memory. The cognitively disabled Linux out-of-memory killer then kicked in, nuking the VM. Thanks, OOM Killer, you’ve been very helpful. Double thanks, jackhole at 188.8.131.52 in the Netherlands. May you rot in hell.
Yes, I could have tuned Apache and Linux better, but the new site is nginx on CentOS 7 and I didn’t want to waste more time on old, tired web servers. So screw it, I pulled the trigger. This battle station is fully operational. Let’s do this.