So I froze Rails for my application. Now I'm getting an error because my script/spin file calls for Mongrel, which was installed as a user gem in my home directory on the server rather than as a server-wide gem. It seems to me Capistrano is not executing as my user on the remote server. Otherwise, it would have access to my user-specific gem bin files, right?
-- Bryan On Feb 2, 8:06 am, Mislav Marohnić <[email protected]> wrote: > Capistrano scripts are running on your local machine, while your app is > deployed and running on a remote server. Capistrano doesn't provide > utilities to set up your deployment environment on the remote server. > Your easiest bet is to vendor (freeze) a specific Rails version in > "vendor/rails" directory of your app. However, if you'd like to pursue this > issue further I would suggest trying a more appropriate mailing list like > rails-talk. > > On Mon, Feb 2, 2009 at 08:41, Bryan Richardson <[email protected]> wrote: > > > Hello all, > > > I'm trying to use Capistrano to deploy a Rails application to a server > > I share with some friends. The global version of Rails is old, and I > > want to use a newer version with my deployment. Thus, I installed > > Rails 2.2.2 for my user only (~/.gems/gems/rails-2.2.2). However, it > > looks like the spawner script I'm calling in script/spin is looking > > for Rails 2.2.2 in the global gems location. I've set the user > > variable in the config/deploy.rb file, but this doesn't seem to help. > > Can anyone tell me how I can configure Capistrano to use user-specific > > gems? > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
