# Freezing 1.1.6 **URL:** \ **Category:** Rails\ **Created:** [May 15, 2008, 2:08am UTC](https://www.ruby-forum.com/t/freezing-1-1-6/137659 "2008-05-15T02:08:17Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![amanda](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/67e7ee/32.png) [@amanda](https://www.ruby-forum.com/u/amanda)\ **Post date:** [May 15, 2008, 2:08am UTC](https://www.ruby-forum.com/t/freezing-1-1-6/137659/1 "2008-05-15T02:08:17Z")
I’ve been slowly working my way backwards through my troubles and I realized that I do have access to the old server so maybe I ought to head back there to figure some of this out. I have an app that is running on rails 1.1.6. I want to move it to a web host that is running 2.0.2. The first step, it seemed to me, was to freeze it. > **[Freezing Rails | Tiger Technologies Support](https://support.tigertech.net/freeze-rails)** > > If you are using Ruby on Rails and want to ensure maximum stability, you should "freeze" the version of Rails you use. But rake rails:freeze:gems didn’t work: [myapp]% rake rails:freeze:gems (in /users/home/somebody/sites/myapp) rake aborted! Don’t know how to build task ‘rails:freeze:gems’ (See full trace by running task with --trace) I tried to specify the version in my environment.rb: RAILS\_GEM\_VERSION = ‘1.1.6’ unless defined? RAILS\_GEM\_VERSION but that isn’t cutting it. It still breaks down when it starts loading gems (line 52, if I comment that out, line 53): 52 require ‘active\_support’ 53 require ‘active\_record’ 54 require ‘action\_controller’ 55 require ‘action\_mailer’ 56 require ‘action\_web\_service’ [http://groups.google.com/group/rubyonrails-talk/browse\_thread/thread/3e8564f6b0885a74/9fec5466dfa034a5#9fec5466dfa034a5](http://groups.google.com/group/rubyonrails-talk/browse_thread/thread/3e8564f6b0885a74/9fec5466dfa034a5#9fec5466dfa034a5) [http://groups.google.com/group/rubyonrails-talk/browse\_thread/thread/d6cd34bbc9d52bc7/03180960f81c452b#03180960f81c452b](http://groups.google.com/group/rubyonrails-talk/browse_thread/thread/d6cd34bbc9d52bc7/03180960f81c452b#03180960f81c452b) ---
**Author:** ![amanda](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/67e7ee/32.png) [@amanda](https://www.ruby-forum.com/u/amanda)\ **Post date:** [May 15, 2008, 2:45am UTC](https://www.ruby-forum.com/t/freezing-1-1-6/137659/2 "2008-05-15T02:45:08Z")
Amanda wrote: > I’ve been slowly working my way backwards through my troubles and I > realized that I do have access to the old server so maybe I ought to > head back there to figure some of this out. > > I have an app that is running on rails 1.1.6. I want to move it to a > web host that is running 2.0.2. > > The first step, it seemed to me, was to freeze it. > [Freezing Rails | Tiger Technologies Support](http://support.tigertech.net/freeze-rails) > > But rake rails:freeze:gems didn’t work: > [myapp]% rake rails:freeze:gems > (in /users/home/somebody/sites/myapp) > rake aborted! > Don’t know how to build task ‘rails:freeze:gems’ hmm… just try downloading 1.1.6 [http://github.com/rails/rails/tarball/v1.1.6](http://github.com/rails/rails/tarball/v1.1.6) and stick this into your vendor/rails directory should just work?