Browse Source

docs(readme): update accessing via ssh

master
Josh Habdas 1 year ago
parent
commit
7d9b18c9c0
Signed by: jhabdas GPG Key ID: B148B31154C75A74
1 changed files with 2 additions and 2 deletions
  1. +2
    -2
      README.md

+ 2
- 2
README.md View File

@ -78,7 +78,7 @@ POSTGRES_PASSWORD=gitea
POSTGRES_DB=gitea
```
Under _General Settings_ set `Site Title`, `SSH Server Domain` and `Gitea Base URL`. These can be changed later in the Gitea `app.ini` config file.
Under _General Settings_ set `Site Title`, `SSH Server Domain`, `SSH Server Port` and `Gitea Base URL`. These can be changed later in the Gitea `app.ini` config file.
Configure the admin user under the _Administrator Account Settings_ then **Install Gitea** to complete initial configuration.
@ -88,7 +88,7 @@ To use the dark theme modify `app.ini` as specified in [Customizing the look of
### Accessing via SSH
Until Traefik [supports TCP](https://github.com/containous/traefik/issues/10) SSH connections to Gitea are exposed directly from the container to the host on port `2222` using the [`ports`](https://docs.docker.com/compose/compose-file/compose-file-v2/#ports) setting in `docker-compose.yml`. While it's possible to bind from the container directly to port `22` on the host chances are your host already has an SSH daemon running on this port.
~~Until Traefik [supports TCP](https://github.com/containous/traefik/issues/10)~~ (see [#4587](https://github.com/containous/traefik/pull/4587)) SSH connections to Gitea are exposed directly from the container to the host on port `2222` using the [`ports`](https://docs.docker.com/compose/compose-file/compose-file-v2/#ports) setting in `docker-compose.yml`. While it's possible to bind from the container directly to port `22` on the host chances are your host already has an SSH daemon running on this port.
To automatically use port `2222` when using `git` to interact with the remote create a `config` file in `~/.ssh/` on your client and add `Port` like:

Loading…
Cancel
Save