Capistrano

WB: If my only problems with Capistrano were a few bugs, I would have submitted patches.

These roles are known to Capistrano (and can be extended for your own purposes).

I have occasionally had serious difficulty 'handing off' a Capistrano config to a customer at the end of a project.

Capistrano works best when paired with a source control system, but it's not required.

Without a saved host key, SSH and Capistrano prompt to verify the key, which breaks the automated deployment.

Listing 5 shows a minimal Capistrano script to push an application to a known set of servers.

Finally, Capistrano is a popular deployment tool used in the Ruby on Rails community.

Capistrano lets us deploy and rollback everywhere; git with github lets us all hack frantically on the same codebase then merge and deploy.

Then, modify your Capistrano recipe (deploy. rb) as shown in Listing 6.

Capistrano is a popular deployment package that acts in a similar manner to Rake.

Rather than checking out the code by hand, a new server bootstraps the Capistrano process.

Capistrano is another popular tool for remote systems administration.

Capistrano supports groups of machines via roles, among hundreds of other features.

You write a script that uses Capistrano's domain-specific language and run various tasks.

Things are certainly looking positive for the future development and support of Capistrano.

Puppet and Capistrano can capture oft-repeated tasks in scripts.

Rewrite the script using Capistrano[4].

This is more work up front, but it means that Capistrano can later manage the server quite easily.