sameersbn / sameersbn/docker-gitlab
Same instance under multiple domains, only serve relative URLs
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Is it even possible to have GitLab work this way? And is it possible to setup this docker images this way?
For example:
Want to run it locally under http://192.168.1.x, but also have it globally under http://git.domain.com and accessible via VPN though http://10.8.x.x
I can only specify one GITLAB_HOST variable, and if its empty it defaults to localhost, most of the functionality works, but for example avatars for projects are served via 'http://{GITLAB_HOST}/uploads/project/avatar/P/P.png' instead of just '/uploads/project/avatar/P/P.png'
Any way to solve this issue?
Thanks
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
The issue names the GITLAB_HOST configuration and project avatar URLs but no files or tests. Start by tracing how the Docker image passes GITLAB_HOST into GitLab and how avatar URLs are generated; done means supporting the described multi-domain setup without hard-coded absolute URLs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100