SoundSoftware Code Site

h1. Moving to Rails 3

h2. Test environment

We have a Redmine 2.2 pristine branch (redmine-2.2) and an integration branch (redmine-2.2-integration) in which to fix errors arising from merging our own changes back in to Redmine 2.2.

For Rails 2, we have been using Ruby Enterprise Edition v1.8.7 with Phusion Passenger v3.0.1.

For Rails 3 we want to use a more mainstream Ruby v1.9.3, with Phusion Passenger v3.0.18.

Ubuntu 10.04 LTS only has Ruby 1.9.1, so we use the Brightbox packages.

<pre>

 $ sudo apt-add-repository ppa:brightbox/ruby-ng

 $ sudo apt-get update

 $ sudo apt-get install ruby1.9.3

 $ sudo gem1.9.3 install rails

 $ sudo gem1.9.3 install passenger

 $ sudo apt-get install libcurl4-openssl-dev

 $ sudo passenger-install-apache2-module 

</pre>

The Passenger installer prints out:

<pre>

Please edit your Apache configuration file, and add these lines:

   LoadModule passenger_module /var/lib/gems/1.9.1/gems/passenger-3.0.18/ext/apache2/mod_passenger.so

   PassengerRoot /var/lib/gems/1.9.1/gems/passenger-3.0.18

   PassengerRuby /usr/bin/ruby1.9.1

</pre>

(Note that the Brightbox PPA "Ruby 1.9.1" is in fact 1.9.3, unlike the Ubuntu repo package which is 1.9.1 -- confusing)

Although the different versions of Ruby and Rails can coexist, the Passenger Apache module can be loaded once per Apache instance only, so introducing the new version will supersede entirely the old one. The Rails version is specified in each application config, but they will all get the same Ruby version.

So, we make the above change (in @mods-available/passenger.load@) and the existing sites break with "Ruby on Rails version '2.3.14' not found" -- fair enough, it isn't installed for the new version of Ruby. Rather than fix this, let's keep the situation simpler to understand by blundering into the world of Rails 3 only.

Now, to the web instance and @hg pull -u; hg update redmine-2.2-integration@.