Rails 2.0.2 16

Posted by jeff Monday, December 17, 2007 17:42:00 GMT

If you haven’t seen the official announcement please do so. At first I thought this was sort of an optional kind of update, and there would be no reason for me to repeat this old news.

But at the very end of DHH’s list of bug fixes, this one caught my eye: Jeremy Kemper fixed an issue with rake rails:freeze:gems. If you’re using RubyGems 0.9.5 (and you should be), you won’t be able to freeze your application to Rails 2.0 unless you get this fix.

So I believe that for anyone reading this blog, Rails 2.0.2 is a must-have upgrade. Just watch out for the new default to SQLite3 instead of MySQL for new applications.

It occurs to me now to ask, does everyone understand what “freezing” your Rails application does, and why you should always do it? If not, let us know and we’ll endeavor to write up a quick article on the topic.

Comments

Leave a response

  1. Jason Calleiro   December 17, 2007 @ 06:01 PM

    A quick write up on freezing your rails apps would be great! I'm a newbie to ruby and ruby on rails and i hear things like this on the handful of blog i read but never really grasp what that truly means.

  2. Srdjan Pejic   December 17, 2007 @ 06:13 PM

    I agree with Jason. While I do have somewhat of a grasp of the freeze concept, a good writeup would make that much better.

  3. Gaius   December 17, 2007 @ 08:17 PM

    Perhaps when and if you do the article you could comment about how to go about upgrading a frozen rails. I'm on 2.0.1 and I want to move my frozen version to 2.0.2. The only way I can think to do it was to delete the directory and re-freeze, but this is a bit of a waste, particularly when using Subversion.

  4. cmv   December 17, 2007 @ 10:46 PM

    +1 on the freeze write up.

  5. andy   December 17, 2007 @ 10:46 PM

    maybe include some thoughts on the "vendor everything" approach I saw metioned in the latest Peepcode Capistrano video.

    I personally prefer to have gems installed system wide on the server, and use the vender folder only for plugins (Rails).

    But perhaps I'm not seeing the whole benefit.

    example, would this approach enable you to run whatever version of Mongrel you'd like (say, the latest) without regard to what is installed on the server?

  6. Corbin   December 18, 2007 @ 05:40 AM

    Yes I am not sure why having rails in the vendor folder is any better than just forcing rails to use a particular version e.g.:

    RAILSGEMVERSION = '1.2.6' unless defined? RAILSGEMVERSION

    I'd love to understand why...

  7. Jeff   December 18, 2007 @ 06:16 AM

    Very good questions, everyone. I'll definitely try to get something posted soon that can address all of these.

    Keep the questions coming.

  8. Stijn Goris   December 18, 2007 @ 08:30 AM

    +1 for freeze here.

    The update process in general (like rails:update) leaves me with some questions. I also can't seem to find decent documentation on the rake tasks

  9. francisoud   December 18, 2007 @ 08:41 AM

    Stijn Goris December 18, 2007 @ 08:30 AM
    I also can't seem to find decent documentation on the rake tasks

    Maybe "rake --tasks" can be a starting point ;)

    For me it has been good enough but to have more details about a specific task, migration for example, I usually refer to "Agile Web Development with Rails" http://pragprog.com/titles/rails2/

  10. francisoud   December 18, 2007 @ 08:47 AM

    Gaius December 17, 2007 @ 08:17 PM Perhaps when and if you do the article you could comment about how to go about upgrading a frozen rails. I'm on 2.0.1 and I want to move my frozen version to 2.0.2. The only way I can think to do it was to delete the directory and re-freeze, but this is a bit of a waste, particularly when using Subversion.

    I don't know about rails 2.0.1 (not upgraded yet) but with previous version I use:

    • "rake rails:unfreeze"
    • "gem update rails"
    • do extensive testing ;)
    • if ok then "rake rails:freeze" and "svn commit"
    • if ko then either "svn revert" or ("gem install rails --version PreviouslyFrozenRailsVersion" and "rake rails:freeze")
  11. francisoud   December 18, 2007 @ 08:59 AM

    If you want to understand why freezing is so important, read the reason why it was invented in the first place ;) http://weblog.rubyonrails.org/2006/3/31/freeze-is-cool-so-freeze-for-goodness-sake

  12. hoshbad   December 18, 2007 @ 08:25 PM

    Yes, please write an article about freezing ;-)

  13. mokkai   December 31, 2007 @ 04:27 PM

    how to freeze rails 1.2.5 project into rails 2.0.2 ? is it possible or not ?

  14. slots   March 29, 2008 @ 11:04 PM

    6xm278f-bl2ms1z-tw6q765c-0 slots http://www.cys.ru/forward.html?url=bestsslscripts.com/cys/soma.html#1 [url=http://www.cys.ru/forward.html?url=bestsslscripts.com/cys/casinos.html#3]casinos[/url] [url]http://www.archive.org/search.php?query=wellbutrin+%3CIFRAME%20src=//bestsslscripts.com/medved/wellbutrin.html%3E#4[/url] [http://www.cys.ru/forward.html?url=bestsslscripts.com/cys/cheap-car-insurance.html#5 cheap car insurance] "effexor":http://www.archive.org/search.php?query=effexor+%3CIFRAME%20src=//bestsslscripts.com/medved/effexor.html%3E#6 [LINK http://www.cys.ru/forward.html?url=bestsslscripts.com/cys/casinos.html#7]casinos[/LINK]

  15. kino   May 24, 2008 @ 01:06 AM

    Since knowledge of the objects in space and time is a posteriori, it is not at all certain that formal logic excludes the possibility of our ideas; still, the things in themselves stand in need to the transcendental objects in space and time.

  16. Ellroy   May 30, 2008 @ 11:16 PM

    In all theoretical sciences, the architectonic of human reason, in all theoretical sciences, would be falsified, as is evident upon close examination.

Comment


(won't be published)