On Aug 27, 10:54 pm, Jamis Buck <[EMAIL PROTECTED]> wrote:
> Jeff,
>
> Yeah, it kind of seems that way, but in fact, doing so would have some
> unfortunately side-effects.
[snip]
Thanks for the explanation, makes sense.
Jeff
--~--~-~--~~~-
On Aug 26, 7:47 pm, Jeff <[EMAIL PROTECTED]> wrote:
> On Aug 26, 5:58 pm, Jamis Buck <[EMAIL PROTECTED]> wrote:
>
>
>
> > You can capture the exit code via the on_request callback:
>
> > ssh.open_channel do |channel|
> > channel.on_request
s. The
> data parameter is a Net::SSH::Buffer object containing the request-
> specific data for the request. For exit-status, this will be a single
> long integer, representing the exit status.
>
> Hope that helps!
Immensely!
Jeff
--~--~-~--~~~---~--~-
ned how to capture stdout and stderr.
Is there a way to also capture the exit code from the remote process?
Some tools that I have to call remotely will return non-zero if they
fail, in which case I want to abort my script.
Thanks!
Jeff
--~--~-~--~~~---~--~~
To u
I've just sent a pull request, mostly because I'm trying to get used
to Git and GitHub's way of doing things and this is a good way to try
that out :) Please let me know if I've goofed in any way!
-Jeff
On Jun 14, 8:16 pm, Jamis Buck <[EMAIL PROTECTED]> wrote:
>
Thanks, that's good to hear. Do you have a preference as to whether I
fork via github and send a pull request whenever I come up with a
patch, or simply make a local git clone of your repo and email the
patch instead? Just getting my feet wet with Git lately =)
-Jeff
On Jun 12, 12:19 pm,
s, I could just put some sort of no-op "normal"
sudo command prior to this capture line (right now it's the first line
in the task) which would ensure the prompt works OK, or I could
manually patch my local copy of the Capistrano gem. Is there another
solution I'm missing?
Th
On May 4, 4:55 pm, Jamis Buck <[EMAIL PROTECTED]> wrote:
> On May 4, 2008, at 3:33 PM, Jeff wrote:
>
> > 1. Just curious as to why cap doesn't use MultiSSH under the hood,
> > since the essence of capistrano (do stuff on multiple servers via ssh)
> > seems to
to some extent.
Thanks again for capistrano!
Jeff
--~--~-~--~~~---~--~~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~--~~~~--~~--~--~---
I've made this mistake several times myself.
Anyone know why cold deploy doesn't just call the setup task
automatically?
Jeff
On Jan 4, 2:05 pm, John M Lauck <[EMAIL PROTECTED]> wrote:
> ...silly me. Thanks Johnathan
>
> On Jan 4, 1:27 pm, Jonathan Weiss <[EMAIL P
On Oct 2, 10:12 am, John Ward <[EMAIL PROTECTED]> wrote:
> I posted recipes for mongrel 2.0 here
>
> http://thinedgeofthewedge.blogspot.com/2007/08/mongrel-and-capistrano...
>
>
>
> Jamis Buck wrote:
> > Is anyone here using cap2 with mongrel_cluster, and can g
as just about to try to upgrade from 1.x and 2.0. We use Apache +
mongrel cluster currently. What would I need to do to get Cap 2.0 to
work with mongrel cluster properly? I checked the Upgrade page on
capify.org but didn't see anything specific. Are the mongrel_cluster
overrides simply not
On Aug 1, 9:11 am, goodieboy <[EMAIL PROTECTED]> wrote:
> OK answered this myself. This is perfect, using a password-less pass-
> phrase doesn't require ssh-agent to be running! :)
Any chance you could post the code that finally worked for y
On Jul 26, 8:48 am, "Jamis Buck" <[EMAIL PROTECTED]> wrote:
> Jeff, yes. Rather than having each SCM module define it's own username
> and password variables, I went with a standardized approach, so that
> it was easier to document. Regardless of the SCM in use, yo
right in thinking that in 1.4, it was called :svn_username? As
part of the upgrade process, do I need to change occurrences
of :svn_username to :scm_username?
Jeff
--~--~-~--~~~---~--~~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more opt
On May 7, 5:03 pm, Jamis Buck <[EMAIL PROTECTED]> wrote:
> Jeff,
>
> The spawner/reaper dance is not specific to fcgi--it's also for
> mongrel. That said, if you are using a cluster of mongrel instances,
> many people are prefering the mongrel_cluster utility to the rai
fcgi.
So for getting a brand new rails app deployed for the first time, I
just need to run cap setup, then cap deploy.
Am I right, or am I missing something?
Jeff
--~--~-~--~~~---~--~~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more option
nded way
to do what I'm trying to do?
Thanks!
Jeff
--~--~-~--~~~---~--~~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~--~~~~--~~--~--~---
18 matches
Mail list logo
