[ANN] Capistrano 2.0

[Jamis Buck]

I fully expect this announcement to be eclipsed by the far more
world-shattering event of the release of Harry Potter #7, but I
suppose it runs in the family. (I have a stagecoach robber in my
family several generations back, whose pièce de résistance happened to
coincide with the sinking of the Titanic.)

Capistrano 2.0 is real.

Install it thus:

gem install capistrano

It's been through four preview releases, and has seen significant
changes since 1.4.1. If you're currently using 1.4.1, be sure to check
out the upgrade documentation (http://www.capify.org/upgrade). If
you're altogether new to Capistrano, you might like to read about
getting started (http://www.capify.org/getting-started).

Since the last preview release (number four, version 1.99.3), the
changes are primarily bug fixes, but the following featureish
modifications snuck in, too:

* The uploader has added a tiny bit of sleep to prevent the CPU from
going bonkers during uploads.
* You can specify the $CAPISTRANO:HOST$ placeholder in the filenames
that you give to "put", and it will be replaced with the actual host
that the file is being uploaded to.

Also, some people reported SFTP uploads were hanging for them. If this
happens to you, try adding the following line to the top of your
recipe file:

set :synchronous_connect, true

That will cause connections to the servers to be established serially,
rather than in parallel, so if you've got a lot of servers that you
are connecting to, it might make things a bit time-consuming. However,
this appeared to work around the hanging SFTP issue.

You can read the complete changelog here:
http://svn.rubyonrails.org/rails/tags/capistrano_2-0-0/CHANGELOG.

KNOWN ISSUES

Yes, there are a few of these. Two are of immediate significance:

# If you try to use the 'put' command to upload a file to two or more
hosts via a gateway, you run a good chance of encountering "corrupted
mac" errors. This is due to design flaws in Net::SSH and Net::SFTP,
and (to my knowledge) cannot be worked around. The current best
practice is to upload to a single host, and then use scp or rsync from
the remote hosts to pull the file.
# A very few people have reported commands hanging inexplicably and
infrequently. I suspect this is also due to flaws in Net::SSH, but I'm
not certain yet.

[Holger Kohnen]

On Sunday 22 July 2007 02:35:21 Jamis Buck wrote:
>   set :synchronous_connect, true

Great, this works for me, thanks for that and the other nice Capistrano
features. Capistrano is awesome.

kind of regards, Holger

[Neil Wilson]

Way to go Jamis. Just what I was waiting for.

On Jul 22, 1:35 am, "Jamis Buck" <ja...@37signals.com> wrote:

> Capistrano 2.0 is real.

[Kenneth Kalmer]

On 7/22/07, Jamis Buck <ja...@37signals.com> wrote:
>
> I fully expect this announcement to be eclipsed by the far more
> world-shattering event of the release of Harry Potter #7, but I
> suppose it runs in the family. (I have a stagecoach robber in my
> family several generations back, whose pièce de résistance happened to
> coincide with the sinking of the Titanic.)
>

Congratulations, and thanks to everyone who made this release
possible! Really looking forward to convert all our Rails projects
over to cap2, and exploring system administration and deployment
possibilities!

--

Kenneth Kalmer
kenneth...@gmail.com

Folding@home stats
http://fah-web.stanford.edu/cgi-bin/main.py?qtype=userpage&username=kenneth%2Ekalmer