I'm still having problems with this one. I tried adding GEM_PATH to the default_environment array, but it didn't seem to have any effect.
Are there certain circumstances under which these settings just won't take hold? From what I've turned up in searching for the solution to this problem, it seems there's a fair bit of inconsistency between webhosts. Actually, I may as well ask. Has anyone solved this sort of problem for deploying apps to Site5 hosting accounts? - Chris On Sep 18, 6:22 am, "Jamis Buck" <[EMAIL PROTECTED]> wrote: > I'm afraid I've never configured an alternative gem path, so I'm not > speaking from direct experience here. But if it simply requires a new > GEM_PATH environment variable, you can simply do this in your > config/deploy.rb: > > default_environment["GEM_PATH"] = "/first/path:/second/path:..." > > In other words, set the complete GEM_PATH. > > - Jamis > > On 9/16/07, Drinkingbird <[EMAIL PROTECTED]> wrote: > > > > > The variable isn't set in either of those files. > > > I should have been clear in the first post that I've set the gem path > > in the rails app environment, and that is working within the app, so I > > know that the gem is properly installed. > > > I've also tried setting the gem path in ~/.ssh/environment, with no > > luck. > > > So, what is the proper way to set the remote gem path in capistrano? > > > - Chris > > > On Sep 16, 12:52 am, "Jamis Buck" <[EMAIL PROTECTED]> wrote: > > > Where are you setting the ENV['GEM_PATH'] bit? In the rakefile? Or in > > > your capfile? > > > > I'd be interested to see whether the cap 2.1 pre-release works for you > > > here. > > > > - Jamis > > > > On 9/13/07, Drinkingbird <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > I've been using capistrano with no issues, deploying a particular app > > > > for a while now. > > > > > Recently I started using ferret to provide search functionality fort > > > > the site, and things have come a bit unstuck. > > > > > When I run the deploy:migrations task, I get this: > > > > > ** [out :: mysite.com] rake aborted! > > > > ** [out :: mysite.com] > > > > ** [out :: mysite.com] no such file to load -- ferret > > > > > although the plain deploy task works, as does "rake db:migrate" > > > > through SSH. > > > > > Ferret is installed in a slightly unusual way on the server. I've > > > > change the GEM_HOME on the server to /home/myuser/gems, and added the > > > > directory to the gem path. > > > > > I've also added this directory to the ENV['GEM_PATH'] variable. > > > > > It seems that for some reason my custom gem path isn't being searched > > > > when the migrations are run through capistrano. Is there any way to > > > > specify that the extra directory should be included? --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
