sameersbn / sameersbn/docker-gitlab
GITLAB_GRAVATAR_ENABLED appears to be a first run only setting
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Setting the GITLAB_GRAVATAR_ENABLED variable to false in my docker-compose.yml file after having run docker-compose up -d once (or more) already does not disable the Gravatar integration. It appears to be a first run only setting. It's not documented as such. Neither here nor upstream.
This option was (re)introduced in 088a58d2ce4cad3b8345f411740600a0b1693316.
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 docker-compose.yml and the GITLAB_GRAVATAR_ENABLED handling, then inspect commit 088a58d2ce4cad3b8345f411740600a0b1693316. Reproduce the behavior by changing the variable after an initial docker-compose up -d and determine whether the setting is intentionally first-run-only. Done means either subsequent runs honor false or the first-run limitation is documented in the relevant project documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100