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-05-05 21:44:49 -06: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 Merge branch 'master' of git://github.com/rmm5t/capistrano into rmm5t/master 2008-05-05 21:44:49 -06:00
test Fix for deploy:pending while using git. git log requires a .. following the from revision even if the to revision isn't specified; otherwise the log goes backwards starting at the from revision instead of finding all newer commits after the current from revision. For example, git log <from_revision>.. is required instead of just git log <from_revision> 2008-05-05 23:07:22 -04:00
capistrano.gemspec version bump, prepping for 2.3 release 2008-05-02 14:47:55 -06:00
CHANGELOG Make sure deploy:check works with :none scm (which has no default command) [#10 tagged:committed state:resolved] 2008-05-05 21:38:09 -06: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 tests all pass 2008-04-27 21:47:23 -06:00
README update README to reflect new dependencies 2008-04-27 21:57:49 -06: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 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.