On Jul 14, 2008, at 10:18 AM, Tim Ferrell wrote: > Jamis Buck wrote: >> On Jul 14, 2008, at 9:50 AM, Michael Richardson wrote: >> >> Note that cap _can_ do that...but you would need to write the tasks >> to >> do it. The default deployment tasks are just opinions codified, and >> as >> such only satisfy the majority of cases, but not all. Cap itself, >> though, can be scripted to support a much larger set of deployment >> scenarios. >> > > Thanks Jamis ... the thing I find a bit difficult to get my head > around > is exactly which tasks are executed on which roles in the default > tasks... Is this documented somewhere?
Alas, no. I'd recommend reading the capistrano/recipes/deploy.rb file, as it is pretty well documented and not as magical as most people seem to fear. (Not magical at all, really.) http://github.com/jamis/capistrano/tree/master/lib/capistrano/recipes/deploy.rb > Also, I currently have in place is a few custom tasks that replace > certain default tasks and then replacement tasks for the cold_deploy > and > deploy tasks that incorporate my custom tasks in the process where I > need them. Is there an easier or better way to override defaults or is > that the way it should/must be done? You've got it right. When you need to change the behavior of one of the "meta" tasks (like deploy:cold or deploy), you basically need to do like you did, and rewrite it. - Jamis --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
