sameersbn / sameersbn/docker-gitlab
how can i have both http and https ?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
How can i have both HTTP and HTTPS / force user using gitlab as HTTPS and can get rawdata of public projects as HTTP content ?
This is my gtlab with loadbalacner:
docker run --restart=always --name gitlab -d --link gitlab-postgresql:postgresql --link gitlab-redis:redisio --publish 10022:22 --publish 10081:80 \
--env 'GITLAB_SSH_PORT=10022' --env 'GITLAB_HOST=git.example.com' --env 'GITLAB_PORT=10443' --env 'GITLAB_HTTPS=true' --env 'SSL_SELF_SIGNED=true' \
--env 'GITLAB_SECRETS_DB_KEY_BASE=123123123' --env 'GITLAB_EMAIL_DISPLAY_NAME=Main Git Repository' \
--env 'SMTP_USER=a11111@gmail.com' --env 'SMTP_PASS=1111' --env 'GITLAB_TIMEZONE=Europe/Berlin' \
--env 'DB_NAME=gitlabhq_production' --env 'DB_USER=gitlab' --env 'GITLAB_ROOT_PASSWORD=123123123' \
--env 'DB_PASS=234234234' \
--volume $(pwd)/storage/data:/home/git/data sameersbn/gitlab:8.8.2
docker run --restart=always --name nginx-loadbalancer -d \
--volume $(pwd)/config:/config \
--publish 10443:443 --publish 10080:80 nginx-loadbalancer entrypoint
But during get data from raw content switch to https port. how can i solve this issue ?
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 two docker run commands and compare the GitLab HTTPS settings with the nginx-loadbalancer port mappings. Trace how raw public-project URLs are generated and whether they preserve the external HTTP or HTTPS scheme. Done means raw content uses the intended protocol while normal GitLab access remains HTTPS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100