commit 15e9ed54d8b2db039fbe7dd76413ad92db40fb9a
tree be278440ff997d9f78dde7e25b827e71e877b195
parent b3deb09d595a9bdb301b1cb8dd4428e6b616704e
tree be278440ff997d9f78dde7e25b827e71e877b195
parent b3deb09d595a9bdb301b1cb8dd4428e6b616704e
| name | age | message | |
|---|---|---|---|
| |
CHANGELOG | ||
| |
MIT-LICENSE | Sun Mar 04 14:25:51 -0800 2007 | |
| |
README | ||
| |
Rakefile | ||
| |
bin/ | Sat Sep 01 08:03:58 -0700 2007 | |
| |
capistrano.gemspec | ||
| |
examples/ | Sun Mar 04 14:25:51 -0800 2007 | |
| |
lib/ | ||
| |
setup.rb | Wed Mar 28 21:48:34 -0700 2007 | |
| |
test/ |
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 originally came bundled with a set of tasks designed for deploying Rails applications. The deployment tasks are now (as of Capistrano 2.0) opt-in and require clients to explicitly put "load 'deploy'" in their recipes. == Dependencies * Net::SSH v2 (http://net-ssh.rubyforge.org) * Net::SFTP v2 (http://net-ssh.rubyforge.org) * Net::SCP v1 (http://net-ssh.rubyforge.org) * Net::SSH::Gateway v1 (http://net-ssh.rubyforge.org) * HighLine (http://highline.rubyforge.org) If you want to run the tests, you'll also need to have the following dependencies installed: * Mocha (http://mocha.rubyforge.org) == Assumptions Capistrano is "opinionated software", which means it has very firm ideas about how things ought to be done, and tries to force those ideas on you. Some of the assumptions behind these opinions are: * You are using SSH to access the remote servers. * You either have the same password to all target machines, or you have public keys in place to allow passwordless access to them. Do not expect these assumptions to change. == Usage In general, you'll use Capistrano as follows: * Create a recipe file ("capfile" or "Capfile"). * Use the +cap+ script to execute your recipe. Use the +cap+ script as follows: cap sometask By default, the script will look for a file called one of +capfile+ or +Capfile+. The +someaction+ text indicates which task to execute. You can do "cap -h" to see all the available options and "cap -T" to see all the available tasks.


