Typo Issues
About a week ago my blog died, as many of you might have noticed. Part of this was due to weird 500 errors that were occurring due my host's policies about renegade processes. Partly they were due to the mysql database not being the proper version for the version of typo I was using, which was also due to the process killer because every time I'd try to run:
I'd wait and wait and wait while the process grew past 100MB and then got the axe. I futzed around with re-running the rake task, trying to find the task manually and finally I started to get frustrated with the whole thing and I had decided to move to Mephisto, another Rails app, but it's more of a CMS than just a blog. I might still move, since they have a blog post converter, but it's only somewhat maintained by it's developers at the moment, and I certainly don't have the time to develop it further. Eventually I deleted some of my older typo installs, installed the typo-4.1.1 version, restored the MySQL database (I managed to completely screw up that thing by manually deleting the session table), ran the rake migration command with the exact rakefile I meant to use
(perhaps the others were spidering all the rakefiles it could find in parent and sibling directories), and letting it "sit" for a while (originally after I had done all of that, it was failing to get to the admin console because it couldn't find the blog with "blog_id==4", which I don't have), then I could log in and everything starting working normally. I think the lesson here is to stay on the stable release branch. Having a host with a backup of your databases is really nice too.
rake db:migrate
I'd wait and wait and wait while the process grew past 100MB and then got the axe. I futzed around with re-running the rake task, trying to find the task manually and finally I started to get frustrated with the whole thing and I had decided to move to Mephisto, another Rails app, but it's more of a CMS than just a blog. I might still move, since they have a blog post converter, but it's only somewhat maintained by it's developers at the moment, and I certainly don't have the time to develop it further. Eventually I deleted some of my older typo installs, installed the typo-4.1.1 version, restored the MySQL database (I managed to completely screw up that thing by manually deleting the session table), ran the rake migration command with the exact rakefile I meant to use
rake -f Rakefile db:migrate
(perhaps the others were spidering all the rakefiles it could find in parent and sibling directories), and letting it "sit" for a while (originally after I had done all of that, it was failing to get to the admin console because it couldn't find the blog with "blog_id==4", which I don't have), then I could log in and everything starting working normally. I think the lesson here is to stay on the stable release branch. Having a host with a backup of your databases is really nice too.
