Fix bundle install running twice when you change your Gemfile about docker-rails-example HOT 4 CLOSED

I wonder if that's because they're using a different CPU architecture or distro where it's not as simple as copying files over and new files need to be created from scratch but most of it works so it's still fast?

I just pushed it (without running it twice), let's see what happens. If it turns out to be broken in some case it can always be patched to add in the 2nd run. If you want to test out the master branch that would be much appreciated.

Here is the commit: 7b08daf

from docker-rails-example.

How about copying bundler dependencies from webpacker like you do for public assets?

something like this would work? I mean once its copied, running bundle install again should be pretty fast.

COPY --chown=ruby:ruby --from=webpacker /app/vendor/bundle /vendor

from docker-rails-example.

Hey, that's a good idea.

I don't think we would even need to run it again if we copy over /usr/local/bundle. Do you see a reason why we would have to?

I tested it here and the COPY step took a second to copy the files and afterwards the project was able to be upped successfully and the tests are passing.

I ran both a run bundle:install and run bundle:update. Also manually upped the project and ran run cmd bundle install which finished very quickly. In all cases the correct thing happened and it was fast.

from docker-rails-example.

Thats great. On our project though (not using docker yet), when I restore the bundler dependencies in semaphoreci, it doesn't seem to work without running the command again, must be some other issue.

from docker-rails-example.