1
0
Fork 0
mirror of https://github.com/capistrano/capistrano synced 2023-03-27 23:21:18 -04:00

Clarify shell requirement. Fixes #1870

This commit is contained in:
William Johnston 2017-10-11 07:25:08 -05:00
parent fcfe3a60de
commit ddba584079
2 changed files with 8 additions and 0 deletions

View file

@ -88,6 +88,10 @@ Likewise, your server(s) will likely need supporting software installed before y
Capistrano is designed to deploy using a single, non-privileged SSH user, using a *non-interactive* SSH session. If your deployment requires `sudo`, interactive prompts, authenticating as one user but running commands as another, you can probably accomplish this with Capistrano, but it may be difficult. Your automated deployments will be much smoother if you can avoid such requirements. Capistrano is designed to deploy using a single, non-privileged SSH user, using a *non-interactive* SSH session. If your deployment requires `sudo`, interactive prompts, authenticating as one user but running commands as another, you can probably accomplish this with Capistrano, but it may be difficult. Your automated deployments will be much smoother if you can avoid such requirements.
#### Shells
Capistrano 3 expects a POSIX shell like Bash or Sh. Shells like tcsh, csh, and such may work, but probably will not.
## Quick start ## Quick start
### Requirements ### Requirements

View file

@ -136,3 +136,7 @@ Capistrano 3 now runs the `deploy:cleanup` task as part of the standard deploy w
```ruby ```ruby
set :keep_releases, 10 set :keep_releases, 10
``` ```
#### POSIX Shell
Capistrano 3 expects a POSIX shell like Bash or Sh. Shells like tcsh, csh, and such may work, but probably will not.