One thing that I've fallen across recently is that there is no way to 'reorder' the hooks.
So if I extend capistrano using the hooks (such as reloading apache after update) in a recipe library then there is no way for the end user to do something 'after update' but before the hook put in by the recipe library (such as updating shared areas). The workaround is to get the user to hook another task (with the 'finalize_update' task being a favourite, even if it is spelt wrong :-). However those hooks look like they need to be an OrderedList of some sort. On 6 Jun, 05:35, Jamis Buck <[EMAIL PROTECTED]> wrote: > === before/after hooks use well-defined server scope === > > Prior to this release, if you defined a before hook using a block, the > block would be executed within the same server scope as the original > task that invoked task that this hook was attached to. (whew!) > > In other words: > > task :first, :roles => :app do > # ... > second > end > > task :second, :roles => :db do > # ... > end > > before :second do > # ... > end > > Prior to this release, when "first" calls "second", the before hook at > the bottom would get called, but it would get called with the :roles => > :app server constraint active, instead of :roles => :db. This preview > release makes those hooks use the server scope of the task they are > attached to. --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
