[Capistrano] Re: problem * `executing deploy:restart'

[Jamis Buck]

You'd probably have to look at the mongrel_cluster recipes to answer the first question. For the latter--I know at one point the mongrel_cluster recipes were not entirely compatible with cap2, but that might have changed recently.

- Jamis

On May 28, 2008, at 2:50 PM, john wrote:

Hi,
can anyone tell me if the 'set :runner, 'my_mongrel_user' will
actually work with the mongrel_cluster/recipes? Or is it just for the
default capistrano tasks? Also can anyone tell me if the
mongrel_cluster/recipes are ok to use with cap 2.3.0?

many thanks,
John

On May 28, 12:17 pm, john <[EMAIL PROTECTED]> wrote:

Hi,
I have a rails on ubuntu deployment stack which consists of:

locally: cap 2.3.0 and all latest deps
server side: apache 2.3, mongrel_cluster, mod_proxy and git on the
same host.

I am connecting via ssh with agent and pass phrase. All is good until
my first deploy:restart task. I have included the mongrel_cluster/
recipes via:

require 'mongrel_cluster/recipes'

inside of my deploy.rb which I think is necessary. For some reason
when the cap deploy hits the 'deploy:restart' task which is the first

sure why. My :user and :runner are both members of the sudoers on the
server.

I have put my deploy.rb here:

http://pastie.caboo.se/204609

Any help or pointer would be greatly appreciated.

many thanks,
John

mongrel task I am prompted for a password and the task fails. I am not

--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

smime.p7s
Description: S/MIME cryptographic signature