Skip to content
Browse files

Clarify low-memory deploy process

  • Loading branch information...
1 parent 3636e98 commit c9dcc09772dfe17ac4efeb79ad08b564e9d7beaa @indirect indirect committed Mar 1, 2010
Showing with 1 addition and 5 deletions.
  1. +1 −5 README.markdown
6 README.markdown
@@ -278,11 +278,7 @@ Explanations of common Bundler use cases can be found in [Using Bundler in Real
### Deploying to memory-constrained servers
-If you are deploying to a server that is very memory-constrained, like
-Dreamhost for example, you should run `bundle package` and check in the
-resulting `Gemfile.lock` and `vendor/cache` directory. Then, when you run
-`bundle install` after deploying, Bundler will not need to do a dependency
-resolution run, which can be very memory-intensive.
+When deploying to a server that is memory-constrained, like Dreamhost, you should run `bundle package` on your local development machine, and then check in the resulting `Gemfile.lock` file and `vendor/cache` directory. The lockfile and cached gems will mean bundler can just install the gems immediately, without contacting any gem servers or using a lot of memory to resolve the dependency tree. On the server, you only need to run `bundle install` after you update your deployed code.
### Other questions

0 comments on commit c9dcc09

Please sign in to comment.
Something went wrong with that request. Please try again.