diff options
| author | Andre Arko <andre@arko.net> | 2010-03-01 10:20:52 -0800 |
|---|---|---|
| committer | Andre Arko <andre@arko.net> | 2010-03-01 10:20:52 -0800 |
| commit | c9dcc09772dfe17ac4efeb79ad08b564e9d7beaa (patch) | |
| tree | dad2922ff2f812bd850256bf0257aff15845907c | |
| parent | 3636e98674abc6187ffeae74c889eac7b194e2e3 (diff) | |
| download | bundler-0.9.10.tar.gz | |
Clarify low-memory deploy process0.9.10
| -rw-r--r-- | README.markdown | 6 |
1 files changed, 1 insertions, 5 deletions
diff --git a/README.markdown b/README.markdown index fba2123e6f..652b99e23d 100644 --- a/README.markdown +++ b/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 |