diff options
author | Andre Arko <andre@arko.net> | 2010-08-24 20:06:26 -0700 |
---|---|---|
committer | Andre Arko <andre@arko.net> | 2010-08-24 20:06:26 -0700 |
commit | 6a6a3654289df99dc0d86f68b354fe697998b3bc (patch) | |
tree | af6ceba2d01d5f11d881f62b56b1ece86d2d186e /UPGRADING.md | |
parent | bbbf9d9da7223edcaae20416e6bd2d78a11350ac (diff) | |
download | bundler-6a6a3654289df99dc0d86f68b354fe697998b3bc.tar.gz |
Add 0.9 to 1.0 note about Passenger
Diffstat (limited to 'UPGRADING.md')
-rw-r--r-- | UPGRADING.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/UPGRADING.md b/UPGRADING.md index 4f76b9a377..905f6a41eb 100644 --- a/UPGRADING.md +++ b/UPGRADING.md @@ -4,6 +4,12 @@ Upgrading from Bundler 0.9 to 1.0 is relatively painless. The Gemfile API is the same, so your old Gemfiles should continue to work. +The "env" file that 0.9 created at `.bundle/environment.rb` has been +removed. As a side effect of this, Passenger will only find your +bundled gems if you install with `bundle install --deployment`. +Alternatively, you can tell Passenger where you gems are installed, +[something like this](http://bit.ly/passenger-gem-home). + The `bundle lock` command is no longer needed, as the Gemfile.lock file is now automatically generated by `bundle install`. If you have not yet done so, add your Gemfile.lock to source control |