sameersbn / sameersbn/docker-gitlab
Log when SSL configuration doesn't check out (and using default nginx config)
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
It would be nice if at start, when checking for our ssl certs and key, to ensure we tell the user if there is a problem (of course, only when they have GITLAB_HTTPS enabled) with those files either not existing, having wrong permissions, or whatever other reason might exist for us to not be able to properly apply the ssl enabled nginx configuration.
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 at the startup check for SSL certificates and keys when GITLAB_HTTPS is enabled, then trace how the nginx configuration is selected. Done means the startup output identifies missing, inaccessible, or otherwise unusable SSL files and makes clear when the default nginx configuration is being used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100