The bundler install time is too long every time. about bundler

[mattbrictson]

Your bundle install should only take a long time on the first deploy. If you have not changed anything in your Gemfile, then subsequent deploys will be very fast. Capistrano bundles gems in shared/bundle so that they are reused across deploys of the same app.

If you have more than one app on the same server (which is never the case in my experience), then the bundled gems are not shared between those apps.

[warrenlalata]

same is happening to me. just stucked with this errors: almost 10 mins now.

also whenever it is running, I cannot connect to my ec2 instance. is this expected?

[tkoutangni]

I had the same issue so this is what i tried to solve it. i remove the releases/ and current/ folder on server and redeploy the app. It was fast this time. Let me know if that works for you too.

[mattbrictson]

Can you verify:

1. You don't accidentally have the .bundle directory checked into git
2. The latest version of bundler (1.6.4) is installed on the server

[wcc526]

Thank you,I want to know why the capistrano bundle install folder is in the shared bundle,why not use the system's bundle folder,If I deploy more project,it will save time.

[mattbrictson]

Bundler's official documentation recommends against using the system location in deployment.
http://bundler.io/v1.6/man/bundle-install.1.html#DEPLOYMENT-MODE

[wcc526]

why Bundler's official documentation recommends against using the system location,I mean in the producion environment.
I don't understand the purpose,why not share the same gem in different project,If they use seperate gem,it takes too long time to bundle install these gems when cap production deploy.

[ijunaid8989]

I am having the same issue. I have only one application.

I installed ruby through RVM there and did nothing else. only the required things. But Its stuck on
``
~/.rvm/bin/rvm default do bundle install --path /home/deployer/apps/evercam-admin/shared/bundle --without development

[cbrandt-it]

Have you found a solution, @errawn ? I'm having the exact same problem.