Ruby on Rails Thursday, December 31, 2015

solved - had a doubled entry overriding the user variable

On Thu, Dec 31, 2015 at 9:58 AM, tom <tomabroad@gmail.com> wrote:
hi, i had rvm system wide, but then switched to a user installation, and now im getting this:

 cap production deploy
DEBUG [18852256] Running /usr/bin/env which passenger as administrator@domain.com
DEBUG [18852256] Command: ( export RVM_BIN_PATH="~/.rvm/bin" ; /usr/bin/env which passenger )
DEBUG [18852256]        /usr/bin/passenger
DEBUG [18852256]
DEBUG [18852256] Finished in 0.481 seconds with exit status 0 (successful).
DEBUG [7976a3d9] Running /usr/local/rvm/bin/rvm version as administrator@domain.com
DEBUG [7976a3d9] Command: ( export RVM_BIN_PATH="~/.rvm/bin" ; /usr/local/rvm/bin/rvm version )
DEBUG [7976a3d9]        bash: /usr/local/rvm/bin/rvm: No such file or directory
DEBUG [7976a3d9]
(Backtrace restricted to imported tasks)
cap aborted!
SSHKit::Runner::ExecuteError: Exception while executing as administrator@domain.com: rvm exit status: 127
rvm stdout: bash: /usr/local/rvm/bin/rvm: No such file or directory
rvm stderr: Nothing written

SSHKit::Command::Failed: rvm exit status: 127
rvm stdout: bash: /usr/local/rvm/bin/rvm: No such file or directory
rvm stderr: Nothing written



this is how my deploy.rb starts

require "rvm/capistrano" # Load RVM's capistrano plugin.

set :user, "administrator"
set :rvm_bin_path, "$HOME/.rvm/bin"
set :default_env, { rvm_bin_path: '~/.rvm/bin' }
set :rvm_type, :user


any ideas?

thx


--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CADQqhMcAE4yqwDy2Tqk4zvBagVz3RBp5yYy3Y3x%3DMg6sCv8cwQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment