mirror of
https://github.com/capistrano/capistrano
synced 2023-03-27 23:21:18 -04:00
Fix incorrect reference to the 'setup' task (closes #10819)
git-svn-id: http://svn.rubyonrails.org/rails/tools/capistrano@8919 5ecf4fe2-1ee6-0310-87b1-e25e094e27de
This commit is contained in:
parent
eceaea75ca
commit
208581ae56
2 changed files with 4 additions and 2 deletions
|
@ -1,5 +1,7 @@
|
|||
*SVN*
|
||||
|
||||
* Fix incorrect reference to the 'setup' task in task documentation [rajeshduggal]
|
||||
|
||||
* Don't try to kill the spawner process on deploy:stop if no spawner process exists [Jamis Buck]
|
||||
|
||||
* Dynamic roles (e.g. role(:app) { "host.name" }) [dmasover]
|
||||
|
|
|
@ -110,11 +110,11 @@ namespace :deploy do
|
|||
desc <<-DESC
|
||||
Prepares one or more servers for deployment. Before you can use any \
|
||||
of the Capistrano deployment tasks with your project, you will need to \
|
||||
make sure all of your servers have been prepared with `cap setup'. When \
|
||||
make sure all of your servers have been prepared with `cap deploy:setup'. When \
|
||||
you add a new server to your cluster, you can easily run the setup task \
|
||||
on just that server by specifying the HOSTS environment variable:
|
||||
|
||||
$ cap HOSTS=new.server.com setup
|
||||
$ cap HOSTS=new.server.com deploy:setup
|
||||
|
||||
It is safe to run this task on servers that have already been set up; it \
|
||||
will not destroy any deployed revisions or data.
|
||||
|
|
Loading…
Add table
Reference in a new issue