Thanks, that sounds like a good approach. Can you point me in the right direction on passing application name and stage in that way, rather than doing -S application_name='xyz'?
On Sep 18, 1:03 pm, Donovan Bray <[email protected]> wrote: > In my scripts I setup tasks for stages and applications, so I do: > > cap <stage> <application> <command> > > I wouldn't automatically call deploy.default as part of setting up the > application because that limits you from doing any arbitrary task with it. > > I also built in some guard code to ensure a stage and application is always > set. > > On Sep 17, 2011, at 1:10 PM, grant <[email protected]> wrote: > > > > > > > > > Hi, > > > I've made some progress using different tasks to deploy different, non- > > rails projects by setting some properties, like scm, deploy_to, etc in > > the task itself then calling deploy.update. I'm wondering if this is a > > reasonable approach, or these should definitely be in different Cap > > files for some reason? > > > Thanks. > > > -- > > * 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 > > athttp://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
