summaryrefslogtreecommitdiffstats
path: root/docs/content/doc/installation/with-docker.en-us.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/content/doc/installation/with-docker.en-us.md')
-rw-r--r--docs/content/doc/installation/with-docker.en-us.md12
1 files changed, 1 insertions, 11 deletions
diff --git a/docs/content/doc/installation/with-docker.en-us.md b/docs/content/doc/installation/with-docker.en-us.md
index 66e596ea4d..c2e7a817c9 100644
--- a/docs/content/doc/installation/with-docker.en-us.md
+++ b/docs/content/doc/installation/with-docker.en-us.md
@@ -389,16 +389,6 @@ In this option, the idea is that the host simply uses the `authorized_keys` that
sudo chmod +x /usr/local/bin/gitea
```
- - For Gitea v1.15.x and earlier. As an administrative user on the host run:
-
- ```bash
- cat <<"EOF" | sudo tee /app/gitea/gitea
- #!/bin/sh
- ssh -p 2222 -o StrictHostKeyChecking=no git@127.0.0.1 "SSH_ORIGINAL_COMMAND=\"$SSH_ORIGINAL_COMMAND\" $0 $@"
- EOF
- sudo chmod +x /app/gitea/gitea
- ```
-
Here is a detailed explanation what is happening when a SSH request is made:
1. The client adds their SSH public key to Gitea using the webpage.
@@ -431,7 +421,7 @@ Never add the `Gitea Host Key` as a SSH key to a user on the Gitea interface.
In this option, the idea is that the host simply uses the `authorized_keys` that gitea creates but at step 8 above we change the shell that the host runs to ssh directly into the docker and then run the shell there. This means that the `gitea` that is then run is the real docker `gitea`.
-- In this case we setup as per SSHing Shim except instead of creating `/usr/local/bin/gitea` or `/app/gitea/gitea`
+- In this case we setup as per SSHing Shim except instead of creating `/usr/local/bin/gitea`
we create a new shell for the git user. As an administrative user on the host run:
```bash