Okay, in the last few hours I have made some progress, but it is still not all the way I want it to.
First thing I did not until just now understand is that I have to issue "cap mongrel:start" to run the task I have defined, and it does not get automatically executed on "cap deploy:start". I have now been able to modify it to the point where I can start mongrel using "cap mongrel:start". I just don't understand why I need that, and why it does not work with "cap deploy:start". One thing that surprised me a lot is that with the code above, deploy:start will fail because it will be executed in the home directory of my capistrano user. So I had to add a cd followed by a semicolon for it to work. I wonder if there is a similar problem with deploy:start. One other very weird thing is this: > /var/www/drklaehn/current$ sudo echo $PATH [sudo] password for olerehmsen: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/ games:/var/lib/gems/1.8/bin > /var/www/drklaehn/current$ sudo mongrel_rails sudo: mongrel_rails: command not found > /var/www/drklaehn/current$ which mongrel_rails /var/lib/gems/1.8/bin/mongrel_rails So with sudo, one does not find mongrel_rails, even though the path is obviously set correctly. Does anyone understand that one? I use "set :use_sudo, false" to make sure this is not the reason, but maybe this leads to again different problems. I have googled a lot, and found some people to use all kinds of stuff: different spin scripts, require 'mongrel_cluster/recipes', set :runner, nil etc. But none of that has worked so far. Any new ideas? --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
