Feature #49799

Persist the SSH connection per deployment

Added by Martin Lipp over 8 years ago. Updated almost 6 years ago.

Won't have this time
Target version:
Start date:
Due date:
% Done:


Estimated time:


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.


Updated by Andreas Wolf over 7 years ago

This should be possible already with a combination of these SSH options:


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.


Updated by Helmut Hummel almost 6 years ago

while this would be nice, I don't see anybody implementing or prioritizing this. However I would not object pull requests in that area ;)

Development of TYPO3 Surf now moved to Github. If you think this is still relevant, please open a bug report or feature request here:



Updated by Helmut Hummel almost 6 years ago

  • Status changed from New to Rejected
  • Priority changed from Should have to Won't have this time

Also available in: Atom PDF