Upgrade an app to the latest version of Hobo

Posted by Tom. This recipe answers 1 Question

Breaking Changes

It’s quite common that there are breaking changes from one version of Hobo to the next. These will settle down once we get to 1.0. In the meantime, there are no general instructions for fixing your app. Have a look at the changelog, any announcements on the blog, or ask in the user group.

Upgrading

Upgrading Hobo is a simple matter of

$ gem update hobo

Or, if you are tracking edge Hobo using git

$ cd vendor/plugins/hobo
$ git pull

You should also re-run the hobo_rapid generator, as some of the assets put in public by that generator may well have changed.

$ ruby script/generate hobo_rapid

For minor upgrades to Hobo that should be enough. Head over to the user group if your app is still not working.

User contributed notes

  • On October 18, 2008 Peeja said:

    If you're keeping your code in a versioned repository (and if you're not, you should), it's also a good idea to commit your code an have a clean working tree before you upgrade. Make the upgrade, result of the generator(s), and any immediate manual fixes a new commit. If something goes wrong in the process, you can always roll back to your working app before the upgrade.

    It's also good to make sure your tests are passing before you upgrade. Then you'll know exactly when you're done dealing with any breaking changes: when your tests all pass again.