First, of all, thank you Jamis, et al. for capistrano.
I'm interested in understanding how I to extend vs. override the
default deploy tasks. For instance, I noticed in the Palmtree gem,
the author writes:
# We need to override the core deployment tasks so
# they use mongrel cluster instead.
namespace :deploy do
desc <<-DESC
Restart the Mongrel processes on the app server by calling
mongrel:cluster:restart.
DESC
task :restart, :roles => :app, :except => { :no_release => true }
do
mongrel.cluster.restart
end
....
So, since the palmtree code is included after the original capiostrano
code, the restart task (which gets called by default for every deploy)
now uses the mongrel code above. Why? Simply because this code is
included after the capistrano code?
What if I want to extend the default deploy tasks to include other
server needs. For instance, if I want to restart a Solr search daemon
AND restart a mongrel cluster?
I do understand that I can write :after_update_code tasks and the
like, but I'm more interested to understand how I can extend the
deploy: restart task to do multiple things (i.e restart mongrel,
restart ferret, restart mylife).
Thanks,
Sean
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
