Feature #49799
Persist the SSH connection per deployment
| Status: | New | Start date: | 2013-07-08 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
In the current version Surf opens a new SSH connection for every shell command. Since some (mostly managed) hosting servers disallow multiple connections opened in short succession the deployment fails. Because of that (and because it seems to be a better practice too) it would be nice to open only one SSH connection per deployment and reuse it for all commands.
History
#1 Updated by Andreas Wolf about 1 year ago
This should be possible already with a combination of these SSH options:
*ControlPersist
*ControlMaster
With ControlPersist set to "on" (or a number as an amount of seconds), the SSH connection is not closed, but moved to the background and reused on the next connect to this host.