Feature request #341: add a keepalive configuration for both FTP and SCP #465
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
|
Hi. This sounds good. I'm on vacation at the minute so I'll take a proper look sometime next week. Cheers! |
Collaborator
|
*still haven't forgotten. Will try take a look this week. |
Author
|
Hi, don't worry you can take all the time you need. The branch won't go anywhere :) |
|
remote-sync still alive? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I'm using this package at work in order to deploy what I write to our test servers. However like most companies out there, there is a nasty firewall cutting the line if there is no activity for a certain amount of time.
In order to avoid this disconnection, keepalive packets can be sent. Lucky for me the base node modules already had this option :) I just added support for this option, defaulting it to 0 and documented the new setting.
This solves issues #341 and #355.