I've been thinking long and hard about this. It's definitely a move
in the right direction, but I think it needs to be approached
differently, which is why I haven't added this to trunk yet.
My current thinking is this: sometime after the next release of
capistrano (which will be Real
sounds like a good idea, I look forward to seeing it.
will you include a way to deploy when the scm is not accessible from
the server?
if not I'll be happy to implement that part, as I realize you don't
need that use case.
thanks
On Dec 23, 11:42 am, Jamis Buck [EMAIL PROTECTED] wrote:
I've
will you be able to disable the stdout? right now mikes patch prints
out a lot of stuff as it loads all the things in .caprc, which is kind
of annoying.
On Dec 23, 8:15 am, Jamis Buck [EMAIL PROTECTED] wrote:
Mike,
Alright, this finally made it in (as of revision 5774). I didn't use
your
Oh, and I should say: cap DOES have a -q flag, which suppresses all
but the most significant output. By default, cap is noisy.
cap -q some_task #- very quite
cap -v some_task #- slightly noisier
cap -vv some_task #- slightly noisier still
cap -vvv some_task #- noisiest (default)
Here it is, Capistrano 1.3.0. Mostly it is just bug fixes, but it
includes a few minor new features.
The new features:
* The sudo() method now supports an :as option, so that you can
specify who the command should be executed as. This defaults to 'root'.
* You can now encode the SSH
