sameersbn / sameersbn/docker-gitlab
Update documentation: for memory_constrained_envs
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
https://docs.gitlab.com/omnibus/settings/memory_constrained_envs.html
Deprecations:
* gitaly['cgroups_count'] has been deprecated since 15.1 and will be removed in 16.0. Use `gitaly['cgroups_repositories_count']` instead.
* gitaly['cgroups_memory_enabled'] has been deprecated since 15.1 and will be removed in 16.0. Use `gitaly['cgroups_memory_bytes'] or gitaly['cgroups_repositories_memory_bytes'] instead.
* gitaly['cgroups_memory_limit'] has been deprecated since 15.1 and will be removed in 16.0. Use `gitaly['cgroups_memory_bytes'] or gitaly['cgroups_repositories_memory_bytes'] instead.
* gitaly['cgroups_cpu_enabled'] has been deprecated since 15.1 and will be removed in 16.0. Use `gitaly['cgroups_cpu_shares'] or gitaly['cgroups_repositories_cpu_shares'] instead.
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
Open the linked memory_constrained_envs documentation page and review its current Gitaly configuration guidance. Update the deprecation notes to reflect the listed replacements, then verify that the page clearly documents the newer settings and removal timeline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100