Declaring two tasks in the same namespace with the same name will
cause the second definition to overwrite the first. What you want is
to chain behavior onto some base implementation. Assuming
mongrel_cluster provides some implementation for deploy:start, all
you have to do, then, is chain the backgroundrb:server:start task to
deploy:start:
after "deploy:start", "backgroundrb:server:start"
Hope that helps,
Jamis
On Jun 18, 2007, at 11:05 AM, Claudio Poli wrote:
>
> hi,
> I extended one recipe and wrote another for capistrano 2, one is for
> mongrel_cluster (thanks halorgium) and the other one is for
> BackgrounDRb.
>
> I require those libraries in deploy.rb, though they share the same
> namespace methods, example:
>
> namespace :deploy do
> desc <<-DESC
> Start the BackgrounDRb processes on the app server by calling
> backgroundrb:server:start
> DESC
> task :start, :roles => :app do
> backgroundrb.server.start
> end
> end
>
> Problem is that when running cap deploy (or cap deploy:cold) only one
> of this task is executed, in this case backgroundrb starts up, but not
> mongrel_cluster. I believe this is because they share the same
> namespace/method, what's the solution for this?
>
> Also, I was having some trouble when writing files.
> mongrel_cluster has a system command to spit out a config file, based
> on parameters, backgroundrb don't (although it has the -l switch).
> So I was trying something like:
>
> YAML.dump(config, File.open("#{brdb_conf}", "w"))
>
> but that couldn't rellay work, because it doesn't respect permissions
> of the connected user, sudo and whatalike, just like run do.
> Maybe it's not possible, but there isn't a wrapper for executing a
> ruby method just like what run do?
>
> Jamis, yesterday I was talking along with halorgium on an idea of
> opening up a capistrano recipes directory, what do you think about?
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
