MirrorHub/forgejo
0
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-11-04 09:19:06 +01:00
Code Issues Projects Releases Packages Wiki Activity

patch (doc): add heading to ssh flow explanation (#20506)

Browse source
This commit is contained in:
Kevin Samuel 2022-07-27 16:06:02 +02:00 committed by GitHub
parent 2ae1675092
commit 3f87525249
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/content/doc/installation/with-docker.en-us.md
View file

@ -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. 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: 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. 1. The client adds their SSH public key to Gitea using the webpage.