Menu

Self-hosted GitLab uses too much memory: keep repositories and pull requests
📰

Self-hosted GitLab uses too much memory: keep repositories and pull requests

DEV Community: gitlab·Wen Ping·about 2 hours ago
#E2hHPMJ1
#devtogitlab#devto#dev#repository#team
Reading 0:00
15s threshold

This article explains how to put repositories and review on a lighter AngusGit when an intranet GitLab is using a large amount of memory and the team only uses those parts. After reading it, you can create repositories under a team, move them together with their history, set the merge method and branch protection, leave builds on Jenkins, and leave artifacts in an artifact repository.

Sign in to AngusGit first. To move one repository, open Settings → Team , click New Team , and set Team Slug to the GitLab group’s English name. In the sidebar, open Repositories → New repository , set the owner to that team, and leave Add a README file , Add .gitignore , and Choose a license unchecked. If any box is checked, the push is rejected because the histories do not match. If this machine has no public key, run ssh-keygen -t ed25519 -C "[email protected]" and register the line from cat ~/.ssh/id_ed25519.pub under Settings → Profile , on the SSH Keys tab. Then run the commands below. Replace the addresses.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.