Message from discussion Capistrano 2.5.3
Received: by 10.90.118.19 with SMTP id q19mr888882agc.22.1228669741524;
Sun, 07 Dec 2008 09:09:01 -0800 (PST)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [22.214.171.124])
by mx.google.com with ESMTP id 22si14508626yxr.1.2008.12.07.09.09.00;
Sun, 07 Dec 2008 09:09:00 -0800 (PST)
Received-SPF: pass (google.com: domain of jamis.b...@gmail.com designates 126.96.36.199 as permitted sender) client-ip=188.8.131.52;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of jamis.b...@gmail.com designates 184.108.40.206 as permitted sender) smtp.mail=jamis.b...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by ey-out-2122.google.com with SMTP id 25so358910eya.25
for <firstname.lastname@example.org>; Sun, 07 Dec 2008 09:08:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
DomainKey-Signature: a=rsa-sha1; c=nofws;
Received: by 10.103.92.10 with SMTP id u10mr888167mul.22.1228669739532;
Sun, 07 Dec 2008 09:08:59 -0800 (PST)
Received: by 10.103.137.15 with HTTP; Sun, 7 Dec 2008 09:08:59 -0800 (PST)
Date: Sun, 7 Dec 2008 10:08:59 -0700
From: "Jamis Buck" <ja...@37signals.com>
Subject: Re: [Capistrano] Re: Capistrano 2.5.3
Content-Type: text/plain; charset=ISO-8859-1
On Sun, Dec 7, 2008 at 9:22 AM, Larry <la...@stupidtuesday.com> wrote:
> I noticed that you were ditching support for Solaris because of
> similar problems. I understand that, too. But the problem is that
> there are undoubtedly a lot more Windows users than Solaris, and
> although *nix is the platform of choice for RoR enthusiasts, the
> number of Rails developers using Windows is rather large and will
> continue to grow. I am no fan of Microsoft, but, like it or not, they
> are the 800 lb. gorilla in the room.
I'm realizing something about myself and Capistrano. I've been burning
out on cap lately, and I've been trying to figure out why.
I wrote Capistrano for me. I didn't write it to have lots of users. I
didn't write it to be a popular solution to a problem. I wrote it to
scratch my itch. It's been a nice side-effect that so many people have
found it useful, but that wasn't my purpose.
I'm burning out because suddenly I'm feeling an obligation to keep
everyone happy. It is a false obligation, though: I'm honestly not
beholden to anyone for Capistrano's maintenance. I've never received a
cent for my work on cap (and I don't want to receive money for
it--that would put me right back in the obligation boat, and with
Something has to give. In this case (and among other things), it's
Windows. Microsoft may be an 800lb gorilla, but it's not _my_ gorilla,
and it's not in _my_ room. If you need to appease the gorilla, that is
(with all due respect) not my problem. If it happens to be your
problem, please feel free to make the time to get acquainted with
Net::SSH and Capistrano, and scratch your itch.
And, frankly, Capistrano is not _it_ when it comes to deployment. If
nothing else, you can always go back and do what everybody did
pre-capistrano: do it by hand.
Now, if you're stuck in Windows by corporate policy, you have my
sympathy. But I'm still not budging on this issue. I will not break my
back or my sanity on Windows troubleshooting any more.
On the other hand, if you're stuck in Windows by choice, you don't
even have my sympathy. :) It is to YOU that I'm speaking, directly,
when I say that if you want Capistrano on Windows, then it's your
responsibility to do something about it. Either you make Cap work on
Windows and send patches upstream, or you write your own solution from
the ground up.
> Is there a previous release that we can back up to that will work with
> Windows? Or can you suggest any other alternatives?
Any Cap 2.x release ought to work fine on windows. If the pageant
thing is biting you, disable ssh agent forwarding:
ssh_options[:forward_agent] = false
If that doesn't work...well, again. It's not my problem anymore. I'm
sorry to come across so callous, but it's what I have to do right now
to keep myself motivated to work on Capistrano at all.