Last night, I started the update from Movable Type 4.1 to Movable Type 5.01. Unfortunately, the database backend (where all of my useless keypresses are stored) for MT wasn’t very excited about being updated, and it took a big dump on me in the middle of the upgrade process. I didn’t think it was that big of a deal, since, being a genius and everything, I performed not just one, but both types of backups before starting the upgrade process. Take that, prematurely released software!
The joke was still on me, however, as it turns out that MT 5 doesn’t support importing from one of the types of backups, and the other backup didn’t work because that format is retardedly specific, and MT’s database schema had changed between the versions1. Basically, what I found out was that I would have to wipe out everything on my webserver, reinstall Movable Type 4.1, upgrade to Movable Type 4.3, backup again, wipe everything out, install MT 5, and then restore the backup from 4.3 to 5. So, yeah, I decided not to do that.
Instead, I elected to give WordPress a spin. It seems pretty okay. I think it’s a little too early to tell which I like best (I already see some strengths and weaknesses for each). We’ll have to see how this goes.
1 Q: Why would someone design a backup system that preserves things like field names in a database instead of simply preserving the content that everyone actually cares about? A: That person would have to be stupid, because there is no good reason to do so.
It seems that it’s that time of the year again; the time when a young server’s thoughts turn to destroying its own file system, along with the most recent backup of that file system. My server seems to be having an especially difficult time of things. I managed to restore all of its files and databases, but it decided to pout by refusing to build key PERL modules for me. I don’t take any shit from machines, so I took off my belt and beat the shit out of it to show it who’s boss.
We seem to have reached an understanding.
In order to preserve our friendship, we both agreed to make some changes. I am going to try to drink less and stop embarrassing the server by pointing out it had processor augmentation surgery. In return, the server is going to try to reliably serve my websites for more than a year and a half at a time without completely melting down. If either of us reneges on the terms of our agreement, the offender will be beaten with a wrench for a period of no less than seven minutes and forty-five seconds.
As a result of our … session … Cone of Ignorance and Mathematician vs. Philosopher are back online. Because of the way I chose to restore the databases, the authors on MvP will have to contact me for their new passwords. Judging by the number of e-mails I got in the month and a half that the server was down (2), my phone won’t be ringing off the hook, but at least things are working again.