/me locks and loads... ;) The main thing I'd like to see (although admittedly I've not delved deep enough into the code base to see if it already exists!) would be a way of capturing whether a cap deploy has been a success or not.
I realise that at the moment you can see this output on the screen, however as we (and many others) move towards continuous deployment etc, we're not going to be running these commands by hand, we'll let jenkins/hudson/etc do it for us. It would also make the notification framework I'm looking at writing (more on this later in the week!) a lot easier as it would enable me to fire one message when the build works and another if it fails. Kind regards, Matt On 15 August 2011 15:17, Lee Hambley <[email protected]> wrote: > It's high time Capistrano got some love, so ask your friends, harass the > DevOps guys, and please come and file your bug reports and feature requests. > Here's my personal short list: > * Improvements to the Capistrano shell > * Improvements to the DSL (I'd love to switch to Thor, but I think it's too > much of a change) > * Improvements to the logging (tone down the verbosity, obscure passwords, > etc) > * Some decent way to globally specify environmental variables for use on the > remote machine (reliably) > Where can we improve this tool, how can we make it easier to use? > Yours, a refreshed project maintainer, Lee > > -- > * You received this message because you are subscribed to the Google Groups > "Capistrano" group. > * To post to this group, send email to [email protected] > * To unsubscribe from this group, send email to > [email protected] For more options, visit this group > at http://groups.google.com/group/capistrano?hl=en -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
