David, I have (which I am preparing to make public) "Informistrano" to solve just this problem of accountability over a variety of methods... it's not fool proof, and frankly any developer who fancied a go could easily circumvent it; but it's notification and accountability non the less!
Regarding the webistrano connection, I can see that passing commands to capistrano directly probably isn't the easiest thing in the world, especially given the number of potential configurations - that said, a lot of people with less-than-crazy deployment strategies swear by webistrano and I'm sure Mathias' project will go down well :) Multistage + Informistrano is where it's at for me - and I'm hoping to release Informistrano in the next few weeks, it's just a mess at the moment and I feel guilty for writing shoddy code :) - Lee 2009/1/23 David Masover <[email protected]> > 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 -~----------~----~----~----~------~----~------~--~---
