How do I manage related gemstones in capistrano deployment?

I am currently just running the following:

after "deploy: update_code", "deploy: bundle"

namespace :deploy do task :bundle do run "cd #{release_path} && bundle install --deployment --without development test staging" end end 

Now this works great, but the binder completes the installation of all the gems to vendor/gems every time. Although I understand the virtues of isolating gems for each release (as opposed to using a shared folder, which (?) Can cause rollback errors and the like), there is certainly a better way to do this, which does not take a lot of time to deploy and save disk space.

+4
source share
1 answer

Things have changed since the release of package 1.0

You do not need to create a custom task from the deployment.

just use require 'bundler/capistrano'

take a look at http://blog.josephholsten.com/2010/09/deploying-with-bundler-and-capistrano/ for more details

+9
source

Source: https://habr.com/ru/post/1337194/


All Articles