On Mar 15, 2010, at 4:15 PM, Roch Delsalle wrote:
I have been running a 1.1.2 RoR app for a few years without upgrading.
I’m now forced to move it since we the current hosting plan is ending.
I would like to know what would be the best way to do it since it has
changed a lot. At the time I was using the localization plugin, and
some really old things.
Yikes! And I thought I had an old app in production on Rails 1.2.2
Depending on how “big” it is, you might find it easier to rewrite it
for 2.3.5 or even jump on 3.0.beta.
To “upgrade”, the path looks something like:
1.1.2 => (1.1.6 =>) 1.2.0 => 1.2.6 => (2.x =>) 2.3.5
You might not need to hit 1.1.6, but gobs of stuff changed in 1.2.0 so
that’s probably a good bet. Whether you need to hit 2.x (where x is
probably 0) might be debatable, but 1.2.6 should have the deprecation
warning for the bigger changes in 2.0.
This assumes that you have good test coverage.
And rewriting would be really hard (for whatever reason).
Of course, if you can vendor rails into your repository, you might be
able to use 1.1.2 even longer. In my case, I have that 1.2.2 app
running under Passenger with ruby-1.8.7 and only had a few minor
issues getting Rails to run on that version (mostly due to iteration
over strings by character–something that ActiveSupport added, but
1.8.7 has baked-in).
Rob B. http://agileconsultingllc.com