Sounds like you've got more than one version of ruby installed, and the
one that's in the default PATH is the old one. :/
You can either use some symlink magic on the host to make sure
everything points to the new one, or you can make sure you're using an
absolute path to rake so that you're getting the one installed for the
right ruby, e.g.:
set :rake, "/opt/local/bin/rake"
- Jamis
On 1/21/09 10:07 AM, goodieboy wrote:
> Hi,
>
> I'm running into problems where the PATH doesn't seem to be correct
> when Cap runs remote commands. For example, when I run cap
> deploy:migrate I get an error saying that RubyGems is too old:
>
> Rails requires RubyGems >= 0.9.4 (you have 0.9.2). Please `gem update
> --system` and try again.
>
> But when I log into the server and run gem -v I get 1.3.1. I created a
> task like: run("which gem") and it gave a path to my old gem command.
> I tried setting the :gem_command variable but that doesn't do anything
> either. So, my question is... how do I get this to work? :)
>
> Matt
> >
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
