In my last post, I made a quick note about how the FriendlyORM had some issues in Postgres. I made a few quick hacks (all in the interest of finishing this up and launching it yesterday). A few hours later, James Golick managed to fix the issues in a special postgres branch. I updated the Github/Twitter proxy with a vendored version of Friendly. If you have to upgrade though, you’ll have to wipe the database. Your steps on Heroku would look like:

Don’t worry, only caching info is stored on the database.

For normal code updates, you only need to perform the first two steps above.

Just out of curiosity, is anyone hosting their own? If you don’t want to mess with the server stuff, you can always just use http://gh-twitter.com without entering your token. Once Github gives into my demands, you’ll be able to just use gh-twitter without any worries.