summaryrefslogtreecommitdiff
path: root/UPGRADING.md
diff options
context:
space:
mode:
authorAndré Arko <andre@arko.net>2012-12-06 23:57:07 -0800
committerAndré Arko <andre@arko.net>2012-12-06 23:57:07 -0800
commit181ef21665655a091c3385a73c85459f304ee4d5 (patch)
tree461b8258bf9f2537e3d6c8de75ce764ebea94df7 /UPGRADING.md
parent9b739e22010b4edf7c90fd14c8fafa0f866b9915 (diff)
downloadbundler-181ef21665655a091c3385a73c85459f304ee4d5.tar.gz
cut out the bit.ly middleman [ci skip]
Diffstat (limited to 'UPGRADING.md')
-rw-r--r--UPGRADING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/UPGRADING.md b/UPGRADING.md
index e50ecfb9b5..3cce388c81 100644
--- a/UPGRADING.md
+++ b/UPGRADING.md
@@ -8,7 +8,7 @@ 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).
+[something like this](http://andre.arko.net/2010/08/16/using-passengerpane-with-gem_home-set/).
The `bundle lock` command is no longer needed, as the
Gemfile.lock file is now automatically generated by `bundle install`.