sameersbn / sameersbn/docker-gitlab
gitlab adds the port number on links
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
clicking on links sometimes redirect to the port mentionned (which doesn't work.)
- docker-compose.yaml config:
...
- GITLAB_HTTPS=true
- SSL_SELF_SIGNED=false
- GITLAB_HOST=gitlab.mutahar.rocks
- GITLAB_PORT=10080
- GITLAB_SSH_PORT=10022
- GITLAB_RELATIVE_URL_ROOT=
- GITLAB_SECRETS_DB_KEY_BASE=[REDACTED]
- GITLAB_SECRETS_SECRET_KEY_BASE=[REDACTED]
- GITLAB_SECRETS_OTP_KEY_BASE=[REDACTED]
...
removing the port will just default to 80 or 443, but i don't want that as i have other services running that uses these ports.
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 with the docker-compose.yaml configuration and reproduce the issue using GITLAB_PORT=10080, GITLAB_HTTPS=true, and the shown host settings. Trace how links are generated and verify that clicking them reaches the configured GitLab host without an unusable port, while other services can continue using ports 80 and 443.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, shell
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100