> So now, I would like to go add a page to the Wiki that says something like: > > If you want to update to a newer version of Rails, here is what you should > do: > > 1) Run "rake test" and make sure that all of your tests pass. > 2) Ensure that you have the newer version of Rails installed (e.g. via "gem > update") > 3) Check in your code using your favorite SCMS. > 4) Edit config/environment.rb and set RAILS_GEM_VERSION to match the version > of Rails to which you wish to update > 5) run "rake update" to update the configuration files (such as boot.rb and > environment.rb), scripts, and javascript files to reflect the newer version > of Rails. > 6) run "rake test" to make sure that all of your tests still pass > 7) 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 reason) > that this same procedure couldn't be used to downgrade an application (say, > for example, if you wanted to use a plugin that only worked with 2.1.0, and > you had been developing in 2.2.2)? I wouldn't expect it to work to switch > from 2.2.2 to, say, 0.3.1, but it seems like it ought to work for anything > in the 2.x.y series. > > --wpd
Worked out perfect for me. I updated a Rails 2.1 (Restful Authentication with all the bells and whistles (new 9/05/08)) app to enable ActiveScaffolding (which works only on rails 2.2. Tnx. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
