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-05-09 04:02:50 +00:00
bin Make sure deploy:cold also runs migrations before starting the app. Have the capify script emit a commented :deploy_to setting. 2007-04-27 05:07:42 +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 Uniquely identify servers based on hostname, port, and username, instead of merely on hostname 2007-05-09 04:02:50 +00:00
test Uniquely identify servers based on hostname, port, and username, instead of merely on hostname 2007-05-09 04:02:50 +00:00
capistrano.gemspec point at new capistrano homepage 2007-04-25 04:25:18 +00:00
CHANGELOG Uniquely identify servers based on hostname, port, and username, instead of merely on hostname 2007-05-09 04:02:50 +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 add deployify script to the gemspec 2007-03-26 16:38:28 +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.