Migrating to Fulcrum 3.1.x on Heroku

[Malcolm Locke]

I've just had to perform this operation, so thought I'd jot down a few
notes for future reference for anyone doing the same.

If you currently have a fulcrum instance running on Heroku's bamboo
stack, there is no path to automatically update your app to the cedar
stack, which is required for the freshly pushed Rails 3.1.x version of
Fulcrum. Instead you need to create a new app, and migrate your
database from the old app to the new one.

I used the following steps to migrate my existing install from bamboo to
cedar. Your mileage may vary, but this worked for me:

- Create a new app on the cedar stack, as described in the Fulcrum
README
- Install the taps gem locally
- Pull the old app database to you local machine. This will overwrite
db/development.sqlite3 by default, so use a different database name if
you don't want this.

$ heroku db:pull --app oldappname

- Push the database to the new app

$ heroku db:push --app newappname

- Test the new app to ensure everything is ok. If you're happy, rename
your old app, and then rename your new app to replace the old app name

$ heroku app:rename oldappbackup --app oldappname
$ heroku app:rename oldappname --app newappname

You can also remove the backup heroku app once you're sure you don't need
it.

Malc