Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rvm1-capistrano3 compatibility #239

Closed
sriedel opened this issue Jul 4, 2017 · 3 comments
Closed

rvm1-capistrano3 compatibility #239

sriedel opened this issue Jul 4, 2017 · 3 comments

Comments

@sriedel
Copy link

sriedel commented Jul 4, 2017

I'm using the rvm1-capistrano3 gem, since the capistrano-rvm gem doesn't work for me and seems to be no longer maintained (see capistrano/rvm#83).

As soon as I added install_plugin Capistrano::Puma line to my Capfile, capistrano could no longer invoke bundler correctly, since the rvm wrapper wasn't being used anymore.

Looking at the code both in rvm1-capistrano3 and here, both are accessing the rvm_bin_maps variable, which seems to be the main point of contention. However I'm not sure as to why, since rvm1-capistrano3 should be loading on demand, if I read the code correctly (https://github.com/rvm/rvm1-capistrano3/blob/master/lib/rvm1/tasks/capistrano3.rake#L41) and capistrano-puma just appends puma and pumactl to the variable. I suspect some order-of-execution issue.

The only thing I've got to actually work is adding set :rvm_map_bins, [ 'rake', 'gem', 'bundle', 'ruby', 'puma', 'pumactl' ] to my deploy.rb file. Not very clean, but Works For Me (TM).

Maybe you can add a pointer in the setup documentation for others having similar issues.

@sinthetix
Copy link

Having the same issue, unfortunately. And set :rvm_map_bins did not work for me :/

@Kagetsuki
Copy link

Same issue - mapping the bins as @sriedel fixed it for me but it's a little concerning.

@github-actions
Copy link

github-actions bot commented Apr 6, 2021

Stale issue message

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants