[Rails-deploy] Re: is there a way to freeze Rails _after_ the fact?

[Jarkko Laine]

On 25.5.2008, at 21.48, Bill Walton wrote:

I've got a managed VPS (the hosting service provides support) and they just did an unannounced upgrade to Rails 2.0. My app is 1.2.x. Is there a way to freeze Rails and the other gems my app needs to a prior version _after_ the fact? I'm really in a bind here.

You should have this line in your config/environment.rb:

#RAILS_GEM_VERSION = '1.2.3' unless defined? RAILS_GEM_VERSION



Cheers,
//jarkko

Just uncomment it and set it to whatever version you want to use. Of course, that gem version must still exist on the system but normally updating gems doesn't remove old versions. Note that you should imho ALWAYS set RAILS_GEM_VERSION unless you have frozen gems (or edge) to your app's vendor directory. Otherwise you will forever be at the mercy of your host messing with the gems.

Thanks,
Bill

--~--~---------~--~----~------------~-------~--~----~

To post to this group, send email to rubyonrails-deployment@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-deployment?hl=en
-~----------~----~----~----~------~----~------~--~---

You received this message because you are subscribed to the Google Groups "Deploying Rails" group.

--
Jarkko Laine
http://jlaine.net
http://dotherightthing.com
http://www.railsecommerce.com
http://odesign.fi

smime.p7s
Description: S/MIME cryptographic signature