I immediately thought multi stage is what he was trying to do; but that's really not the only thing he was trying to do.
He was creating the right tasks nut he was trying to create a 'meta' task that serially called the methods of each configured stage. So he can call them individually and optionally together. If I read his code correctly On Oct 3, 2011, at 1:45 PM, Lee Hambley <lee.hamb...@gmail.com> wrote: > You might want to look here, it's really not pretty – but it worked as a > proof of concept, there has to be a nicer way though: > > https://github.com/leehambley/capistrano-yaml-multistage/blob/master/Capfile#L29 > > Long story short, that's a Rails 2.x app where I wanted to be able to do > multistage without requiring multi-stage. > > - Lee > -- > * You received this message because you are subscribed to the Google Groups > "Capistrano" group. > * To post to this group, send email to capistrano@googlegroups.com > * To unsubscribe from this group, send email to > capistrano+unsubscr...@googlegroups.com For more options, visit this group at > http://groups.google.com/group/capistrano?hl=en -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to capistrano@googlegroups.com * To unsubscribe from this group, send email to capistrano+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
