Make sure you view this installation guide from the branch (version) of GitLab you would like to install (for example, 11-7-stable).
Since installations from source don't use runit for process supervision, SidekiqĬan't be terminated and its memory usage grows over time. Omnibus packages solve this by letting the Sidekiq terminate gracefully if it uses too much memory.Īfter this termination runit detects Sidekiq is not running and starts it. On heavily used GitLab instances the memory usage of the Sidekiq background worker grows over time. One reason the Omnibus package is more reliable is its use of runit to restart any of the GitLab processes in case one crashes. Since an installation from source is a lot of work and error prone we strongly recommend the fast and reliable Omnibus package installation (deb/rpm). Consider the Omnibus package installation If you find a bug/error in this guide, submit a merge requestĬontributing guide. They changed the location of directories or run services as the wrong user. For example, many people run into permission problems because Make sure you don't violate any assumptions GitLab makes about Use caution when you deviateįrom this guide. The following steps have been known to work. Need, this is one of the few installation scripts that actually work out of the box. This guide is long because it covers many cases and includes all commands you If you want to install on RHEL/CentOS, we recommend using the Read requirements.md for hardware and operating system requirements. It was created for and tested on Debian/Ubuntu operating systems.
Other installation options, see the main installation page. To set up a development installation or for many This is the official installation guide to set up a production GitLab server
0 kommentar(er)
