sameersbn / sameersbn/docker-gitlab
some problem about external_url
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Sorry for asking another question about external_url. I known that this parmater is not offered in this docker. And it generated by the GITLAB_HOST and GITLAB_PORT. I have a reverse proxy like nginx on my server so I can't set the port to 80. I set the GITLAB_PORT to 30000, but when I use LFS, the file will upload to the http://{HOST}:{PORT}, not http://{HOST}
The problem is that external port like 30000 can't be connected from Internet, I can only access to the sever by some port like 80,22 etc. So the file can not be uploaded to the 30000. How can I solve it?
#1418 #1043 #302
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 external_url behavior described for GITLAB_HOST, GITLAB_PORT, Docker, nginx, and LFS uploads. Reproduce the generated upload URL through the reverse proxy and confirm that completion means LFS uses a publicly reachable URL and port rather than the internal port.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git, nginx
- Domain
- devops, infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100