The most notable fix is the lingering issue with deploying from a git
repository, where you'd get "Unable to resolve revision" errors. Those
are hopefully laid to rest, now.
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.
Perhaps a virtual machine could solve your peoblems. I run linux but
I have windows in a virtual machine (virtualbox) for testing purposes.
Virtualbox allows you to share directories with your virtual machine
(you could also use samba) which makes it very easy for me to test.
If you are deploying to linux you could simply deploy form a linux
virtual machine. You could even develop on the virtual machine too!
If you are deploying to windows I guess that would make it much
harder. In that case I would like to suggest powerfolder. It will
take care of moving files around (although won't do all other nice
things cap does so you'll have to roll those yourself).
One other thing you might consider is jruby and glassfish. Deployment
is via WAR files but again you don't get all the nice things you get
with cap. Glassfish and other java containers are well supported in
Just some suggestions. Good luck.
I'd like to see something like that organize independently of me. If
the windows community wants a dedicated leader to represent them, I'd
hope someone would step forward, fork capistrano on github, and
proceed to garner support for their initiative. But I really don't
want to appoint someone.