I think the issue is probably using ask from cap that was spawned via a system() call
Note that in his deploy he has several tasks that use system and starts another cap as a sub shell. Which you CAN do, but if it prompts for something it will stall because system won't let you interact with the underlying shell. You would have to use something like popen3 and a block with regexs looking for those prompts and supply the appropriate answers from the parent cap. Or you could pass those things to the sub cap via environment variables. There is a cap command line option to set cap variables you might check into that and you just make sure that the sub cap has all of the info it needs so it won't ask for it at run time. On Nov 16, 2011, at 8:41 AM, Craig White <[email protected]> wrote: > > On Nov 16, 2011, at 9:35 AM, Lee Hambley wrote: > >> Did you come up with some way to fork multiple parallel deploys, of multiple >> projects? >> >> It sounds very much like you are doing something very wrong. > ---- > no question about it - I am doing something very wrong ;-) > > I am working on meshing it all back into the one single 'deploy' namespace > but I have learned much in this 'wrong' process so I do have more to bring to > the table now. > > I think I am getting somewhere now - thanks to you and to Donovan for all the > help. > > Craig > > -- > * You received this message because you are subscribed to the Google Groups > "Capistrano" group. > * To post to this group, send email to [email protected] > * To unsubscribe from this group, send email to > [email protected] 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 [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
