diff options
| author | Andre Arko <andre@arko.net> | 2010-02-23 12:26:40 -0800 |
|---|---|---|
| committer | Andre Arko <andre@arko.net> | 2010-02-23 13:55:38 -0800 |
| commit | fb658b99eb5f63329ba33e8b1bd92f5e34a5ee46 (patch) | |
| tree | b670fe308adde0cb2d3d10e4793bcf88f999a4dc | |
| parent | 9cd7f5befe395b204fc49d5f3316a6b5a245e16a (diff) | |
| download | bundler-0.9.8.tar.gz | |
Specific directions regarding not checking in .bundle0.9.8
| -rw-r--r-- | README.markdown | 13 |
1 files changed, 9 insertions, 4 deletions
diff --git a/README.markdown b/README.markdown index 44a4be63a7..b39c9565d7 100644 --- a/README.markdown +++ b/README.markdown @@ -118,10 +118,15 @@ The command `bundle lock` will lock the bundle to the current set of resolved gems. This ensures that, until the lock file is removed, `bundle install` and `Bundle.setup` will always activate the same gems. -When you are distributing your application, you should add the Gemfile.lock -file to your source control, so that the set of libraries your code will -run against are fixed. Simply run `bundle install` after checking out or -deploying your code to ensure your libraries are present. +When you are distributing your application, you should add the Gemfile and +Gemfile.lock files to your source control, so that the set of libraries your +code will run against are fixed. Simply run `bundle install` after checking +out or deploying your code to ensure your libraries are present. + +DO NOT add the .bundle directory to your source control. The files there are +internal to bundler and vary between machines. If you are using git, you can +exclude all machine-specific bundler files by adding a single line to your +.gitignore file containing `.bundle`. ### Running the application |