number 9

Now that the dust has settled a little , I thought it was time to upgrade the blog to 4.0.x.

I was running typo 2.6.0 with rails frozen at 1.0.0 , so to be honest I was expecting trouble. WEBrick ran so fast on my dummy run I thought it was worth the risk.

If you’re thinking of trying it yourself:

CYA

• backup everything, including the database
• switch your typo theme back to ‘azure’

The last one saves you a lot of hassle if you’re using a ‘tweaked’ theme – if typo can’t find default.rhtml, it won’t run (it’s not as easy to switch themes from the console as it used to be, as the Settings model has been replaced).

fitter, happier

• download and extract the typo tarball (gems on textdrive are a pain in the arse.) – this includes rails 1.1.6 in vendor¹/.
• copy over your existing config/database.yml
• migrate the database

 rasputnik typo-4.0.2 $ RAILS_ENV=production rake migrate

Watch it Just Work (it does on postgresql, anyway),
start it up and have a poke around.

start chopping

On Textdrive, they recently enforced resource limits. After a minute or two I started getting 500 errors as the fcgi backends bloated up and were killed off.
Luckily I’d been warned about this.

• go into ‘text filters’ under the admin screens and disable any text filters you don’t use (I’m textile only here)
• sidebars have to be removed manually , like so:

 rasputnik typo/ $ cd components/plugins/sidebars
 rasputnik sidebars $ ls
 aimpresence               delicious_controller.rb    tada
 aimpresence_controller.rb flickr                      tada_controller.rb
 amazon                    flickr_controller.rb        tag
 amazon_controller.rb      fortythree                 tag_controller.rb
 ...
 ...
 ...
 rasputnik sidebars $ rm -r forty* backpack* amazon* upcoming*
 rasputnik sidebars $ # restart typo
 rasputnik sidebars $ killall -9 ruby && ~/bin/spawn-typo.sh

That should save you a few Mb. I’ve still had the preview pane crash once while I was writing this, but otherwise it seems a lot happier.

UPDATE – crash bang wallop

Well it’s been a month, and it’s finally stablized. Make sure to do the extra steps here (mainly removing Sparklines) if you’re resource restricted.

¹ actually, it doesn’t. Looks like someone dropped a bollock (run ‘rake rails:freeze:gems’ if you want to lock it down).