sameersbn / sameersbn/docker-gitlab
Is it possible to deploy Gitaly on a separate server with sameersbn/gitlab Docker image?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hello,
I'm experiencing slowness on a selfhosted GitLab instance with the sameersbn/gitlab Docker image on a baremetal server.
I'd like to make access to the issue and merge request pages load faster.
Information about the baremetal server:
- Intel® Xeon® D-1531 CPU - 6C/12T - 2.2 GHz
- SSD
- 32GB DDR4
I think the slowdowns happens when git rebase or git merge are executed on the server.
Maybe also git clones executed by GitLab-CI jobs.
I think it's the Gitaly service that performs the git actions. If that's correct, I would like to run Gitaly on a different server.
Questions :
- is it possible to run
Gitalyseparately with thesameersbn/gitlabDocker image? - do you have an example of this type of installation?
Thank you in advance for your comments.
Best regards,
Stephane
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
The issue names no repository files, tests, or entry points to inspect. Begin by identifying how the Docker image configures GitLab and Gitaly, then document whether separate-server deployment is supported and what an example installation would require.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100