sameersbn / sameersbn/docker-gitlab
default GITLAB_SSH_PORT leads to wrong SSH repository URLs
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Starting the container with no GITLAB_SSH_PORT configured (using the default 22) leads to wrong ssh URLs for projects.
Example:
git@example.com:path/to/my/project.git --> : whitout port
Expected paths:
- either:
ssh://git@example.com/path/to/my/project.git - or:
ssh://git@example.com:22/path/to/my/project.git
The ssh:// prefix is also missing. Is this the expected behavior?
Using a different port generates correct URLs (:<PORT>/).
The GITLAB_PORT environment variable is also not provided, but here the HTTP URLs are correct.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing container startup configuration for GITLAB_SSH_PORT and compare URL generation with the default 22 and a custom port. Done means projects receive a valid ssh:// repository URL when the default is used, while HTTP URLs remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git, shell
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100