Versions:

   - Ruby: 2.1.1p76
   - Capistrano: 3.1.0
   - Capistrano-rvm: 0.1.1
   - Rails: 4.1.0rc2
   
Platform:

   - Working on: Ubuntu
   - Deploying to: Ubuntu


Hi there,

I just deployed a Rails app using Capistrano 3 (and RVM, via the gem 
'capistrano-rvm').

But Rails was not recognized:

     $ rails -v

...returned...

     The program 'rails' can be found in the following packages:
      * rails
      * ruby-railties-3.2
     Ask your administrator to install one of them


So I checked out Capistrano's debug log and saw it runs this command during 
deployment:

     /usr/local/rvm/bin/rvm default do bundle install --binstubs 
/home/deploy/shared/bin --path /home/deploy/shared/bundle --without 
development test --deployment --quiet

...and Rails (and all other gems) really are installed in: 
/home/deploy/shared/bundle
Now...

     $ rvm current

...returns...

     ruby-2.1.1@rails410rc2

...which (I believe) means that the gems should have been installed into: 
/usr/local/rvm/gems/ruby-2.1.1/gems - but they weren't: Rails (and the 
other gems) is not there.

Why does it install into "/home/deploy/shared/bundle"?
Aren't the gems 'capistrano' and 'capistrano-rvm' supposed to install into 
the "$ rvm current" gemset (or the one set in deploy), during deployment? 
(Specifying the gemset or not didn't change anything.)

What am I missing?

FWIW, in deploy.rb, I have specified:

     set :rvm_type, :system # system means: /usr/local/rvm
     set :rvm_ruby_version, 'ruby-2.1.1@rails410rc2'

-- 
You received this message because you are subscribed to the Google Groups 
"Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/capistrano/bae28bbf-6b50-4cca-b63a-d9f54c707887%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to