Gitlab-server Environment Construction

1. Requirements for installing Gitlab

UNIX-derived versions supported by the operating system

• Ubuntu
• Debian
• Centos
• Red Hat Enterprise Linux (packages and commands using CentOS)
• Scientific Linux (packages and commands using CentOS)
• Oracle Linux (packages and commands using CentOS)

Unsupported Unix-derived version

• OS X
• Arch Linux
• Fedora
• Gentoo
• Freebsd

These unsupported Unix-derived versions can also be manually compiled and installed Gitlab.

Non-UNIX operating systems (Windows)

Gitlab is specifically developed for the UNIX operating system. GitLab cannot be run on the Windows operating system, and we have not recently considered supporting Windows. You can install Gitlab on a Linux virtual machine or on Docker.

Ruby version

GitLab requires Ruby (MRI) 2.3, and since GitLab 8.13 no longer supports 2.3 of the following versions.

We recommend using a standard MRI interpreter to run Ruby. Although most ruby developers like JRuby and Rubinius. But Gitlab needs the native gems.

Hardware Requirements Storage

The size of the storage space depends largely on the size of the GIT repository you will store. But according to rule of thumb ( rule of thumb) you should consider leaving more room to store backups of the Git repository.

If you want to use elastic storage space, you can consider using the LVM architecture when allocating partitions, so that you can add more storage space by adding the hard disk when you need to empty it later.

In addition, you can hang on to a sub-volume that supports NFS, such as Nas, SAN, AWS, EBS.

If your server has enough memory and CPU processing performance, the Gitlab response speed is mainly limited by the drive's seek time. Using a faster hard drive (7200 RPM) or SSD drive will greatly improve the responsiveness of the Gitlab.

Cpu

• 1 Core CPU supports up to 100 users, all workers and background tasks work in the same core this will cause the Gitlab service to respond somewhat slowly.
• The 2 core supports 500 users, which is also the official recommended minimum standard.
• 4 Core supports 2,000 users.
• 8 Core supports 5,000 users.
• 16 core supports 10,000 users.
• 32 Core supports 20,000 users.
• 64 core supports 40,000 users.

Memory

Installation using Gitlab requires at least 4GB of available memory (RAM + Swap)! Because the operating system and other running applications also use memory, it is important to note that the current server has at least 4GB of available memory before installing Gitlab. Less than 4GB of memory can cause a variety of bizarre problems when reconfigure, and 500 errors often occur during use.

• 1GB physical memory + 3GB swap partition is the minimum requirement, but we strongly oppose the use of such a configuration.
• The 2GB physical memory + 2GB swap partition supports 100 users, but the service response can be slow.
• 4GB Physical Memory supports 100 users and is the official recommended configuration.
• 8GB of physical memory supports 1,000 of users.
• 16GB of physical memory supports 2,000 of users.
• 32GB of physical memory supports 4,000 of users.
• 64GB of physical memory supports 8,000 of users.
• 128GB of physical memory supports 16,000 of users.
• 256GB of physical memory supports 32,000 of users.

Even if your server has enough RAM, allocate at least 2GB of swap partition to the server. Because using swap partitions can reduce the chance of Gitlab errors when your available memory fluctuates.

Note: Sidekiq's 25 workers when viewing a process (top or htop) will see that it displays each worker individually, but they are shared memory allocations because SIDEKIQ is a multithreaded program.

2. Installation

Open Connection: https://about.gitlab.com/downloads/

Like I choose to be CentOS6.

There will be installation steps, in addition to the Chinese version of the installation steps

Http://www.jianshu.com/p/7a0d6917e009?mType=Group

Gitlab-server Environment Construction