Enable ssh access on gitea #57
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
For security and maintenance reasons the container should not map any ports to the host when traefik is in play. The mappning can be done inside Traefik or change the env vars to a propper port and Traefik can discover it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Configure gitea to be accessed by ssh. This is done by setting the variables:
SSH_PORT: port displayed in clone urlSSH_LISTEN_PORT: port for the built-in ssh serverBesides that, it's necessary to map container port 222 to host port 22.
With these changes, one can clone a repository using
ssh://git@<hostname>:222/<username>/<repository>.git.