sameersbn / sameersbn/docker-gitlab
Setting up registry
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
The actual documentation shows two different examples. The docker-compose yaml is different from the mentioned env vars in the registry documentation.
I actually use nginx as reverse proxy with ssl termination for gitlab via gitlab.domain.at. Gitlab itself is setup through docker-compose.yml. I use a byued wildcard certificate for the domain.
What I want to achieve?
- I want to add a registry which is integrated into Gitlab.
- The registry should be available for me directly from my workstation
- The registry should be available in gitlab for some projects.
- The registry should be available through
registry.domain.at
Could anybody paste his working snippets here, which are working?
Cheers,
Josef
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
Compare the registry documentation's examples and environment variables with the mentioned docker-compose.yml setup. Review how the nginx reverse proxy, GitLab integration, and registry.domain.at access are documented. Done means the documentation provides one consistent, working configuration for workstation and GitLab access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, nginx
- Domain
- devops, documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100