Improve SSH docs around ptys and interactive shells #3795
Merged
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.
There has been some confusion around why sometimes you don't get a shell prompt when using Lagoon SSH. This change aims to clarify what happens when you use ssh and when you need to force pty allocation.
I noticed that we advise people to specify port 22 even though that is the default. So I removed that bit.
I also took the opportunity to remove the advice to ignore host keys, since both the ssh core and ssh portal services provide static host keys these days. If you don't want to remove that yet I can push it in a separate PR.
General Checklist
Affected Issues have been mentioned in the Closing issues sectionDatabase Migrations
If your PR contains a database migation, it MUST be the latest in date order alphabeticallyClosing issues
n/a