Skip to content

Commit

Permalink
Default to installing gems on system
Browse files Browse the repository at this point in the history
There are good reasons for vendoring gems for production deployments,
but in my experience, vendoring in development has given my teams more
trouble than the default behavior installing gems on the system.

Existing development environments will continue to use vendor/ until
they modify/remove .bundle/config, because these are mounted with the
source code. This will now slow docker image builds, since .dockerignore
now includes vendor/ and .bundle/.
  • Loading branch information
nilbus committed Jul 20, 2017
1 parent 6ca82a3 commit 7d962e0
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion bin/setup
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ fi

# Set up Ruby dependencies via Bundler
gem install bundler --conservative
bundle check || bundle install --path=vendor/bundle
bundle check || bundle install

# Set up the database and add seed data
bundle exec rake db:from_scratch
Expand Down

0 comments on commit 7d962e0

Please sign in to comment.