Simplify bundler config so "bundle install" does the right thing by default #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This also makes it so that when we
ONBUILD RUN bundle install
it doesn't create.bundle/config
in our precious, pristine application directory, and makes all the bundler-installed Gems show up ingem list
.I'm also sneaking in a change to the
onbuild
variants that makesbundle install
just fail if you've updated yourGemfile
but not yourGemfile.lock
, since that bit me pretty hard while testing this (ie,bundle install
was silently updatingGemfile.lock
, which changes were then clobbered by theCOPY . /usr/src/app
and the application wouldn't run). I think this might actually be the real issue in docker-library/rails#11, too.