Just to be contrary: On Thu, Jan 22, 2009 at 4:40 PM, Mathias Meyer <[email protected]>wrote:
> > - Accountability: Who deployed when and what I suppose it's more absolute accountability, but I had a task which automatically generated a tag and an email for each deploy. Unless someone's deliberately trying to frame someone else, you pretty much know who deployed, when, and what. - Shared recipes: All projects can share recipes (which are in turn > basically snippets containing tasks, etc. that are glued together into > a capfile right before the deployment) The default Capfile loads from vendor/plugins, so what I've been doing is putting common recipes into plugins, and applying appropriate ones to each project. - Easy setup of multi-stage environments Multistage also makes this easy. I'm not saying Webistrano is a bad thing, but I do think this kind of thing might also make sense for Cap directly, especially now that you've got a way to transparently pass tasks through to Webistrano for those who want it. --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
