e00a7faba0
Why and how to enable this is covered in the docs being changed here. This requires gitlab-org/gitlab-shell@2e8b670 ("Add support for SSH certificate authentication", 2018-06-14) which has been merged in and tagged as 8.0.0, so GITLAB_SHELL_VERSION needs to be bumped. Merging this closes gitlab-org/gitlab-ce#34572 see gitlab-org/gitlab-shell!207 for the gitlab-shell MR. Implementation notes: - The APIs being changed here are all internal, and their sole consumer is gitlab-shell. - Most of the changed code is a MR to gitlab-shell, see the gitlab-org/gitlab-shell!207 MR. That change covers why only some of the internal methods get a new "username" parameter, and why some others only get a "user_id".
1.1 KiB
1.1 KiB
Performing Operations in GitLab
Keep your GitLab instance up and running smoothly.
- Clean up Redis sessions: Prior to GitLab 7.3, user sessions did not automatically expire from Redis. If you have been running a large GitLab server (thousands of users) since before GitLab 7.3 we recommend cleaning up stale sessions to compact the Redis database after you upgrade to GitLab 7.3.
- Moving repositories: Moving all repositories managed by GitLab to another file system or another server.
- Sidekiq job throttling: Throttle Sidekiq queues that to prioritize important jobs.
- Sidekiq MemoryKiller: Configure Sidekiq MemoryKiller to restart Sidekiq.
- Unicorn: Understand Unicorn and unicorn-worker-killer.
- Speed up SSH operations by Authorizing SSH users via a fast, indexed lookup to the GitLab database, and/or by doing away with user SSH keys stored on GitLab entirely in favor of SSH certificates.