Why not require them in the main capfile? (Use Dir[] to iterate over
them if you have to), they could inject their namespaces themselves.
should create a global cap -T listing as well.
On Apr 8, 2008, at 9:10 AM, Adam Keys wrote:
>
> We've got a product that is composed of multiple daemons and Rails
> applications. Each daemon or application has its own Capfile. What I
> want to do is create one Capfile "to rule them all". So I want to say
> "cap product:deploy" and run deploy in every daemon and application
> under product. Further, if one of those subsidiary deploys fails, I
> want every prior deploy to rollback.
>
> I've got a really ugly version of this working, but yeah, its ugly.
> What I do right now is call 'cap -T' in each subfolder and then create
> a namespaced task that invokes that task by calling "system('cap
> #{task}')". To deploy everything, I iterate over all the subfolders
> running deploy[1].
>
> Has anyone done this before? Is there a simpler way than
> "introspecting" the Capfiles from the task list?
>
> [1] In reality, its evolved to where I need to run specific tasks from
> specific apps in order, rather than naively iterating and calling
> deploy
>
> --
> ~akk
> http://therealadam.com
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
