diff options
| author | Kevin Samuel <kevin.nl.samuel@gmail.com> | 2022-07-27 16:06:02 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-07-27 10:06:02 -0400 |
| commit | 3f8752524969c52f573c85ac5007c0e91e02b201 (patch) | |
| tree | 9c9fc20a5f9c1f36ba50ec67289ad17e0dd9002a /docs | |
| parent | 2ae1675092ebe300ed88397a0eae5ca1b3a5443c (diff) | |
| download | gitea-3f8752524969c52f573c85ac5007c0e91e02b201.tar.gz gitea-3f8752524969c52f573c85ac5007c0e91e02b201.zip | |
patch (doc): add heading to ssh flow explanation (#20506)
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/content/doc/installation/with-docker.en-us.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/content/doc/installation/with-docker.en-us.md b/docs/content/doc/installation/with-docker.en-us.md index c2e7a817c9..940b38aa75 100644 --- a/docs/content/doc/installation/with-docker.en-us.md +++ b/docs/content/doc/installation/with-docker.en-us.md @@ -309,6 +309,8 @@ To set required TOKEN and SECRET values, consider using Gitea's built-in [genera Since SSH is running inside the container, SSH needs to be passed through from the host to the container if SSH support is desired. One option would be to run the container SSH on a non-standard port (or moving the host port to a non-standard port). Another option which might be more straightforward is for Gitea users to ssh to a Gitea user on the host which will then relay those connections to the docker. +### Understanding SSH access to Gitea (without passthrough) + To understand what needs to happen, you first need to understand what happens without passthrough. So we will try to explain this: 1. The client adds their SSH public key to Gitea using the webpage. |