public
Fork of jamis/capistrano
Description: Remote multi-server automation tool
Homepage: http://www.capify.org
Clone URL: git://github.com/rmm5t/capistrano.git
name age message
file CHANGELOG Sat Feb 24 12:29:21 -0800 2007 version bump [jamis]
file MIT-LICENSE Sun Mar 05 19:48:35 -0800 2006 part 2, rename switchtower -> capistrano [jamis]
file README Sun Mar 05 19:48:35 -0800 2006 part 2, rename switchtower -> capistrano [jamis]
file Rakefile Thu Jul 06 07:22:30 -0700 2006 Add :clean task, and bump capistrano version [jamis]
file THANKS Sat Aug 26 23:55:15 -0700 2006 Add SCM module for Mercurial from Matthew Elder... [jamis]
directory bin/ Sun Mar 05 19:48:35 -0800 2006 part 2, rename switchtower -> capistrano [jamis]
file capistrano.gemspec Sun Aug 27 02:53:49 -0700 2006 Fix gemspec to include license file, etc. [jamis]
directory examples/ Wed Aug 03 05:59:03 -0700 2005 Initial commit of the new switchtower utility [jamis]
directory lib/ Sat Feb 24 12:29:21 -0800 2007 version bump [jamis]
file setup.rb Mon Oct 10 18:43:28 -0700 2005 Have setup.rb create a switchtower.cmd file on ... [jamis]
directory test/ Sat Feb 24 12:20:43 -0800 2007 Pass --no-auth-cache to subversion [jamis]
README
= Capistrano

Capistrano is a utility and framework for executing commands in parallel on multiple remote machines, via SSH. It uses a 
simple DSL (borrowed in part from Rake, http://rake.rubyforge.org/) that allows you to define _tasks_, which may be 
applied to machines in certain roles. It also supports tunneling connections via some gateway machine to allow 
operations to be performed behind VPN's and firewalls.

Capistrano was originally designed to simplify and automate deployment of web applications to distributed environments, 
and so it comes with many tasks predefined for that ("update_code" and "deploy", for instance).

== Dependencies

Capistrano depends upon the Net::SSH library by Jamis Buck (http://net-ssh.rubyforge.org). Net::SSH itself depends on 
the Needle library (http://needle.rubyforge.org), also by Jamis Buck.

== Assumptions

In keeping with Rails' "convention over configuration", Capistrano makes several assumptions about how you will use it 
(most, if not all, of which may be explicitly overridden):

* You are writing web applications and want to use Capistrano to deploy them.
* You are using Ruby on Rails (http://www.rubyonrails.com) to build your apps.
* You are using Subversion (http://subversion.tigris.org/) to manage your source code.
* You are running your apps using FastCGI, together with Rails' spinner/reaper utilities.

As with the rest of Rails, if you can abide by these assumptions, you can use Capistrano "out of the box". If any of 
these assumptions do not hold, you'll need to make some adjustments to your deployment recipe files.

== Usage

More documentation is always pending, but you'll want to see the user manual for detailed usage instructions. (The 
manual is online at http://manuals.rubyonrails.org/read/book/17).

In general, you'll use Capistrano as follows:

* Create a deployment recipe ("deploy.rb") for your application. You can use the sample recipe in examples/sample.rb as 
a starting point.
* Use the +cap+ script to execute your recipe (see below).

Use the +cap+ script as follows:

    cap -vvv someaction

By default, the script will look for a file called one of <tt>config/deploy</tt>, <tt>config/deploy.rb</tt>, 
<tt>capistrano</tt>, or <tt>capistrano.rb</tt>. You can the <tt>-v</tt> switch multiple times (as shown) to increase the 
verbosity of the output. The +someaction+ text indicates which action to execute.