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
2008-02-22 03:38:08 +00:00
bin capify-generated Capfile will autoload all recipes from vendor/plugins/*/recipes/*.rb 2007-09-01 15:03:58 +00:00
examples THANKS file is not applicable anymore. Bring various other files up-to-date with reality. 2007-03-04 22:25:51 +00:00
lib Distributed git support for better operability with remote_cache strategy (closes #11137) 2008-02-22 03:38:08 +00:00
test Distributed git support for better operability with remote_cache strategy (closes #11137) 2008-02-22 03:38:08 +00:00
capistrano.gemspec make sure capistrano only tries to load Net::SSH and Net::SFTP versions less than 1.99.0 2008-01-30 05:31:15 +00:00
CHANGELOG Distributed git support for better operability with remote_cache strategy (closes #11137) 2008-02-22 03:38:08 +00:00
MIT-LICENSE THANKS file is not applicable anymore. Bring various other files up-to-date with reality. 2007-03-04 22:25:51 +00:00
Rakefile Start writing tests for the deployment code. Make the copy strategy checkout to a customizable tmpdir, instead of merely using cwd 2007-04-27 02:20:21 +00:00
README version bump, add some known issues to the README 2007-07-21 22:25:12 +00:00
setup.rb Add deploy:check test for verifying that dependencies are in order for deploying 2007-03-29 04:48:34 +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 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 and Net::SFTP (http://net-ssh.rubyforge.org)
* Needle (via Net::SSH)
* 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.

== KNOWN ISSUES

* Using "put" to upload a file to two or more hosts when a gateway is in effect has a good chance of crashing with a "corrupt mac detected" error. This is due to a bug in Net::SSH.
* Running commands may rarely hang inexplicably. This appears to be specific only to certain platforms. Most people will never see this behavior.