1
0
Fork 0
mirror of https://github.com/capistrano/capistrano synced 2023-03-27 23:21:18 -04:00
Remote multi-server automation tool
Find a file
2007-01-04 04:17:01 +00:00
bin part 2, rename switchtower -> capistrano 2006-03-06 03:48:35 +00:00
examples Initial commit of the new switchtower utility 2005-08-03 12:59:03 +00:00
lib fix connection problems when using gateways (closes #6913) 2007-01-04 04:17:01 +00:00
test Allow SSH user and port to be encoded in the hostname strings (excellent job, Ezra!) closes #6547 2006-11-11 04:21:55 +00:00
capistrano.gemspec Fix gemspec to include license file, etc. 2006-08-27 09:53:49 +00:00
CHANGELOG fix connection problems when using gateways (closes #6913) 2007-01-04 04:17:01 +00:00
MIT-LICENSE part 2, rename switchtower -> capistrano 2006-03-06 03:48:35 +00:00
Rakefile Add :clean task, and bump capistrano version 2006-07-06 14:22:30 +00:00
README part 2, rename switchtower -> capistrano 2006-03-06 03:48:35 +00:00
setup.rb Have setup.rb create a switchtower.cmd file on Win32 platforms 2005-10-11 01:43:28 +00:00
THANKS Add SCM module for Mercurial from Matthew Elder (closes #4150) 2006-08-27 06:55:15 +00:00

= 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.