On Tue, Dec 9, 2008 at 10:38 AM, Codeblogger firstname.lastname@example.org
what do your tests/specs tell you? Do they pass?
I forgot to mention that all of the tests pass before and after running the
$ rake rails:update
The main reason that I forgot to mention that was that, ummm… erhhh…
Well, you see, at the time I wrote that, it wasn’t strictly true. But
And yes, Craig, that should have been “rake rails:update” not “rake
rails:upgrade”… that was a silly typo on my part. Also, I had
used gem to update my rails installation.
So now, I would like to go add a page to the Wiki that says something
If you want to update to a newer version of Rails, here is what you
- Run “rake test” and make sure that all of your tests pass.
- Ensure that you have the newer version of Rails installed (e.g. via
- Check in your code using your favorite SCMS.
- Edit config/environment.rb and set RAILS_GEM_VERSION to match the
of Rails to which you wish to update
- run “rake update” to update the configuration files (such as boot.rb
- run “rake test” to make sure that all of your tests still pass
- Fire up your browser and make sure things look “normal” (for suitable
definition of “normal”).
Does this sound about right to folks? Is there any reason (within
that this same procedure couldn’t be used to downgrade an application
for example, if you wanted to use a plugin that only worked with 2.1.0,
you had been developing in 2.2.2)? I wouldn’t expect it to work to
from 2.2.2 to, say, 0.3.1, but it seems like it ought to work for
in the 2.x.y series.