New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot access PATH or gems from inside Signal #3
Comments
This is most likely not a Signal issue but has to do with Passenger. http://www.icoretech.org/2009/08/passenger-mod_rails-path-on-leopard-snow-leopard/ |
Thanks Manuel, will put that link in the README. |
I followed this advice, but it still can't find RVM
I have RVM installed, and it works fine when I run |
Ok. That icoretech blog post you are linking to is ancient, and no longer works Found the right answer here: In your passenger vhost file you can do this to set the path:
|
Here's the error I get now.
|
When Passenger is executed, I think it uses the user that is the owner from the application but with the environmnet variables from the root user, something like this: su deploy -c "rvm list" try executing this as root to analyze the output, maybe you need to install rvm as system wide. |
When I set up Signal as described and start a build, I get the output "sh: rake: not found".
Seems like "Kernel.system" cannot access my PATH. When I replace "rake" with "/opt/ruby-enterprise-1.8.6-20090610/bin/rake", I get an error message that the gem flog is not found when the metrics are build, although the gem is installed. When I execute the "rake build" command from the command line, everything works fine.
The text was updated successfully, but these errors were encountered: