Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Specific directions regarding not checking in .bundle

  • Loading branch information...
commit fb658b99eb5f63329ba33e8b1bd92f5e34a5ee46 1 parent 9cd7f5b
@indirect indirect authored
Showing with 9 additions and 4 deletions.
  1. +9 −4 README.markdown
View
13 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
Please sign in to comment.
Something went wrong with that request. Please try again.