Closed bratish closed 10 years ago
rvm get stable --auto-dotfiles
does reset your shell initialization files to load RVM properly as it would have been done on first installation of RVM, this can not have influence on what happens in cap ...
as Capistrano:
source ~/.rvm/scripts/rvm
in ~/.bash_login
)PATH
in ~/.bashrc
- so this should not change anythingI'm sorry but I see no connection here, to be sure clean up ~/.bash_login
and ~/.bashrc
from any signs of rvm
and try again, you can revert rvm configuration by running:
~/.rvm/bin/rvm get stable --auto-dotfiles
closing the ticket as there is no connection, please let me know if you find it and I will reopen.
I have developed a new Rails (4.1.4) app in JRuby (1.7.10) and I have been deploying it with Capistrano v3 on a remote vps for sometime. Now all of a sudden the deployer script can't access the repository at Bitbucket. The error looks like:
Although when I log into the remote server and run the same command it successfully executes and connects Bitbucket repo.
This is how the Gemfile looks like:
Capfile:
deploy.rb:
One thing to note here, I was constantly getting an warning from rvm
So I ran
rvm get stable --auto-dotfiles
and I think the issue started after this point. But this is what I am assuming. I might be wrong. I tried to reinstall the rvm of the server bycap production rvm1:install:rvm
, but that didn't help.Can anybody suggest what went wrong?