{"id":3410,"date":"2010-08-18T00:00:00","date_gmt":"2010-08-17T22:00:00","guid":{"rendered":"http:\/\/www.theill.com\/blog\/2010\/08\/18\/upgraded-shoutsms-from-rails-2-3-8-to-rails-3-in-five-minutes\/"},"modified":"2010-08-18T00:00:00","modified_gmt":"2010-08-17T22:00:00","slug":"upgraded-shoutsms-from-rails-2-3-8-to-rails-3-in-five-minutes","status":"publish","type":"post","link":"https:\/\/www.theill.com\/blog\/2010\/08\/18\/upgraded-shoutsms-from-rails-2-3-8-to-rails-3-in-five-minutes\/","title":{"rendered":"Upgraded ShoutSMS from Rails 2.3.8 to Rails 3 in five minutes"},"content":{"rendered":"
Today I wanted to try how easy it would be to upgrade our existing ShoutSMS<\/a> (pretty small) rails application from 2.3.8 to latest Rails 3 release candidate (currently rc3). Without taking our test suite into consideration it took around five minutes with help from the official rails_upgrade[1] plugin. This is fast, yes, but considering the size of this app and possible pitfalls I am not looking forward to upgrade our larger projects.<\/p>\n These are the basic steps to perform<\/p>\n This did most of the work for me. I needed to patch a bit in my new “application.rb” file (e.g. replace RAILS_ROOT with Rails.root, RAILS_ENV with Rails.env, etc).<\/p>\n Notice, the rails_upgrade plugin might suggest to change “ I needed to upgrade ActiveMerchant but it was a simple<\/p>\n and then patch my Gemfile with correct version<\/p>\n It was also needed to go through each ERb and update block helpers. Rake task “rake rails:upgrade:check” can be used multiple times to check if you’re near the end.<\/p>\n I had a couple of “f.error_messages” warnings as well. It’s suggested to install “rails plugin install git:\/\/github.com\/rails\/dynamic_form.git” but I made a partial instead to have complete control over my displayed error messages.<\/p>\n For more general upgrade tips & tricks you might consider viewing part 1<\/a>, part 2<\/a> and part 3<\/a> of the “Upgrading to Rails 3” Railscasts series.<\/p>\n","protected":false},"excerpt":{"rendered":" Today I wanted to try how easy it would be to upgrade our existing ShoutSMS (pretty small) rails application from 2.3.8 to latest Rails 3 release candidate (currently rc3). Without taking our test suite into consideration it took around five minutes with help from the official rails_upgrade[1] plugin. This is fast, yes, but considering the … Continue reading Upgraded ShoutSMS from Rails 2.3.8 to Rails 3 in five minutes<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"amp_status":"","spay_email":"","jetpack_publicize_message":""},"categories":[1],"tags":[],"jetpack_featured_media_url":"","jetpack_publicize_connections":[],"yoast_head":"\n\n
<% @object.each do |p| %><\/code>” blocks to “
<%= @object.each do |p| %><\/code>” but I don’t see this should be done.<\/p>\n
$ gem update activemerchant\n<\/code><\/pre>\n
gem 'activemerchant', '1.7.1', :require => 'active_merchant'\n<\/code><\/pre>\n