Ara, The block on block syntax of Ruby is a little alien to developers that lack your experience - (and I count myself amongst them) - I'd be interested in hearing your opinion on some of the ideas I proposed in this article on our wiki; whilst I think there's a time and a place for your approach, I'm not sure how many of these problems it could solve?
Or, by not really concentrating on this thread, am I about to make a fool of myself :) - Wiki Article: http://wiki.capify.org/index.php?title=Handling_The_Unexpected Lee Hambley 2009/1/12 Jamis Buck <ja...@37signals.com> > > I totally agree, Ara. That approach gets a hearty endorsement from me. > Still, it'd be nice to make it easier to do basic shell scripting > directly via Capistrano. Even if it was a helper that just uploaded the > script to /tmp on the remote servers and invoked it. > > - Jamis > > On 1/12/09 10:21 AM, ara.t.howard wrote: > > > > On Jan 11, 2009, at 9:29 PM, Jamis Buck wrote: > > > >>> more clear anyway, though I'm definitely not sure how one could do > >>> "&"... > > > > > > fork{ fork{ system command } and exit! } and Process.wait # this is > > '&' > > > > the biggest issue, really, is people doing crappy shell scripting that > > should be done in ruby. what we do is make rake tasks to perform any > > key operation, they all cap run command simply looking like > > > > run 'rake some:thing:like:this' > > > > which vastly simplifies getting deployment right. > > > > just food for thought. > > > > cheers. > > > > a @ http://codeforpeople.com/ > > -- > > we can deny everything, except that we have the possibility of being > > better. simply reflect on that. > > h.h. the 14th dalai lama > > > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to capistrano-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
