From a5647c12af8be6d34385b78df7f9d6c8216f918b Mon Sep 17 00:00:00 2001 From: Mikel Lindsaar Date: Wed, 3 Feb 2010 14:26:28 +1100 Subject: Fixing up the idea of bundle and freezing gems --- railties/guides/source/3_0_release_notes.textile | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'railties/guides/source') diff --git a/railties/guides/source/3_0_release_notes.textile b/railties/guides/source/3_0_release_notes.textile index e8d9248646..b9f00cad61 100644 --- a/railties/guides/source/3_0_release_notes.textile +++ b/railties/guides/source/3_0_release_notes.textile @@ -83,7 +83,9 @@ More information: - "Using bundler":http://yehudakatz.com/2009/11/03/using-the-n h4. Living on the Edge -Due to the use of +Gemfile+, your Rails app is "frozen" by default, that is, all the gems you depend on are kept in your vendor directory, these gems are copied from your system gems by default or from gemcutter. If you want to bundle straight from the Git repository, you can pass the edge flag: +Due to the use of the +Bundler+ gem with +Gemfile+, you can "freeze" your Rails app at any time through the bundle command, so the concept of rake freeze has been dropped. + +If you want to bundle straight from the Git repository, you can pass the edge flag: $ rails myapp --edge -- cgit v1.2.3