Having an app with only a single model for caching data, there is no worry about database migration. A nice opportunity for starting out new:
rvm use 1.9.1 gem install rails --pre rails basement-rails3 cd basement-rails3 heroku create basement-rails3 --stack bamboo-mri-1.9.1
business as usual?
Not really… Having Yehuda Katz as a core developer of Rails 3, it’s no surprise they adopted the Merb approach of just using one executable for everything. So the ‘script’ folder now contains just a ‘rails’ script. Creating controllers, running the server, jumping into the console - all through the ‘rails’ command:
rails -h => [...] => generate Generate new code (short-cut alias: "g") => console Start the Rails console (short-cut alias: "c") => server Start the Rails server (short-cut alias: "s") => [...]
I appreciate the shortcuts! No more discussions about what shortcut to use for ‘script/server’ (ss is not an option in germany…)!
Rails 3 has changed the way of working with gems. It uses bundler to deal with dependencies. Beeing a big fan of Java’s dependency management tools like Ivy or Maven, I think that separating out the dependency issue is good idea.
All dependencies are now defined in a separate ‘Gemfile’ using an easy dsl to manage the gems:
gem "rails", "3.0.0.beta" [...] gem "sqlite3-ruby", :require => "sqlite3" [...] group :test do gem "test-unit", "1.2.3" end
I had some trouble getting bundler working on my machine, but after reinstalling Rails 3 AFTER the bundler gem, everything worked fine.
The only Rails plugin in my app is Haml and I was confident that it would play well with the latest Rails version. Never the less I was pleased to find RailsPlugins.org where one can check the compatibility of plugins with Rails 3.
escaping vs. html_safe
There were just very little changes to the existing codebase in my application. Despite one thing though, that forced changes to nearly all of the wrapper objects that are used to encapsulate the data that is coming from external services like twitter. The Problem is that Rails 3 has a strict way of dealing with escaping. Every string rendered into the view will be escaped unless it is ‘html_safe’. Since my application is using a lot of pregenerated content with inline html, adding ‘html_safe’ markers is inevitable:
def content @json["content"]["$t"].html_safe end
Ruby 1.9 is different
The biggest pile of migration problems resulted from using Ruby 1.9.1. The latest Ruby version is a lot faster, but it has changed some of the core functionality. The ‘enum_with_index’ method for example is replaced with an ‘each_with_index’ method on a hash.
Using old YAML files resulted in some strange behavior as these files have changed format slightly (because of the new symbol style that Ruby 1.9 is using, I guess):
# old id: home # new :id: home
Ruby 1.9 also changed the way of handling unicode characters. Using these in code forces the developer to put a magic comment in the first line of the ruby file:
# coding: utf-8 [...]
Most of the new Rails 3 stuff just works, but there are some reasons why it is still beta:
# rails console won't quit with controll-c but exits without error typing ö.ö rails c => Loading development environment (Rails 3.0.0.beta) ruby-1.9.1-p378 > ö.ö ^C # rails help doesn't work for commands rails -h => [...] => All commands can be run with -h for more information. rails generate -h => Could not find generator -h.