I would argue that overriding the default tasks is exactly what he should do. His deployment logic is split between the two projects. In the first project (which contains the migrations), he'd run `cap deploy:cold` to get the application kick-started. In his second project, he wants to skip the migration process, but there's no reason his cap command should differ for what is essentially the same task - to kick-start the application.
Overriding the tasks he needs to in this manner has the benefit of providing a consistent interface to the task of deployment, and hiding the actual deployment logic in deployment recipes specific to each application... Encapsulation ftw. Best, Mason On Apr 7, 2008, at 12:24 PM, Tim Carey-Smith wrote: > > On 7/04/2008, at 11:28 AM, Rafael G. wrote: >> >> You can overwrite cold task in your deploy.rb file: > > It would seem to me that you should consider not changing the default > behaviour of the 'deploy:cold' task (even if it is just for this > application). > Having a new task which does the 'deploy:update' and 'deploy:start' > would make it more apparent that you are doing something out of the > ordinary. > > In most of the deployments I have done, the 'deploy:start' and > 'deploy:restart' do exactly the same thing, that being tell god [1] to > restart the app servers for this application. > What this means is that the 'deploy:cold' and 'deploy:migrations' > tasks are basically the same. > > Cheers, > Tim > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
