Additional Notes : In order to get a proper Ruby & Git setup we build them from source
```
## Overview
Loading
Loading
@@ -37,8 +37,9 @@ This guide does not disable any of them, we simply configure them as they were i
The GitLab installation consists of setting up the following components:
1. Install the base operating system (CentOS 6.5 Minimal) and Packages / Dependencies
1. Install the base operating system (CentOS 6.8 Minimal) and Packages / Dependencies
1. Ruby
1. Go
1. System Users
1. Database
1. Redis
Loading
Loading
@@ -48,9 +49,9 @@ The GitLab installation consists of setting up the following components:
----------
## 1. Installing the operating system (CentOS 6.5 Minimal)
## 1. Installing the operating system (CentOS 6.8 Minimal)
We start with a completely clean CentOS 6.5 "minimal" installation which can be
We start with a completely clean CentOS 6.8 "minimal" installation which can be
accomplished by downloading the appropriate installation iso file. Just boot the
system of the iso file and install the system.
Loading
Loading
@@ -89,46 +90,39 @@ Now install the `epel-release-6-8.noarch` package, which will enable EPEL reposi
**Note:** Don't mind the `x86_64`, if you install on a i686 system you can use the same commands.
### Add PUIAS Computational repository
### Add Remi's RPM repository
The [PUIAS Computational][PUIAS] repository is a part of [PUIAS/Springdale Linux][SDL],
a custom Red Hat® distribution maintained by [Princeton University][PU] and the
[Institute for Advanced Study][IAS]. We take advantage of the PUIAS
Computational repository to obtain a git v1.8.x package since the base CentOS
repositories only provide v1.7.1 which is not compatible with GitLab.
Although the PUIAS offers an RPM to install the repo, it requires the
other PUIAS repos as a dependency, so you'll have to add it manually.
Otherwise you can install git from source (instructions below).
[Remi's RPM Repository][REMI] is unofficial repository for Centos/RHEL that provides latest versions of some software. We take advantage of Remi's RPM repository to obtain up-to-date version of Redis.
Download PUIAS repo:
Download the GPG key for Remi's repository and install it on your system:
# For reStructuredText markup language support, install required package:
yum -y install python-docutils
### Install mail server
In order to receive mail notifications, make sure to install a
Loading
Loading
@@ -168,19 +153,23 @@ To use and configure sendmail instead of postfix see [Advanced Email Configurati
### Configure the default editor
During this installation some files will need to be edited manually.
You can choose between editors such as nano, vi, vim, etc.
In this case we will use vim as the default editor for consistency.
If you are familiar with vim set it as default editor with the commands below.
# Install vim and set as default editor
yum -y install vim-enhanced
ln -s /usr/bin/vim /usr/bin/editor
To remove this alias in the future:
rm -i /usr/bin/editor
### Install Git from Source
### Install Git from Source (optional)
Make sure Git is version 1.7.10 or higher, for example 1.7.12 or 1.8.4
Make sure Git is version 2.7.4 or higher
git --version
Loading
Loading
@@ -195,8 +184,8 @@ Install the pre-requisite files for Git compilation:
Download and extract it:
mkdir /tmp/git && cd /tmp/git
curl --progress https://www.kernel.org/pub/software/scm/git/git-2.1.3.tar.gz | tar xz
cd git-2.1.3/
curl --progress https://www.kernel.org/pub/software/scm/git/git-2.9.0.tar.gz | tar xz
cd git-2.9.0
./configure
make
make prefix=/usr/local install
Loading
Loading
@@ -206,7 +195,7 @@ Make sure Git is in your `$PATH`:
which git
You might have to logout and login again for the `$PATH` to take effect.
**Note:** When editing `config/gitlab.yml` (step 6), change the git `bin_path` to `/usr/local/bin/git`.
**Note:** When editing `config/gitlab.yml` (step 7), change the git `bin_path` to `/usr/local/bin/git`.
----------
Loading
Loading
@@ -214,7 +203,7 @@ You might have to logout and login again for the `$PATH` to take effect.
The use of ruby version managers such as [RVM](http://rvm.io/), [rbenv](https://github.com/sstephenson/rbenv) or [chruby](https://github.com/postmodern/chruby) with GitLab in production frequently leads to hard to diagnose problems. Version managers are not supported and we strongly advise everyone to follow the instructions below to use a system ruby.
Remove the old Ruby 1.8 package if present. GitLab only supports the Ruby 2.0+ release series:
Remove the old Ruby 1.8 package if present. GitLab only supports the Ruby 2.1 release series:
yum remove ruby
Loading
Loading
@@ -226,8 +215,8 @@ Remove any other Ruby build if it is still present:
Download Ruby and compile it:
mkdir /tmp/ruby && cd /tmp/ruby
curl --progress ftp://ftp.ruby-lang.org/pub/ruby/2.1/ruby-2.1.2.tar.gz | tar xz
cd ruby-2.1.2
curl --progress https://cache.ruby-lang.org/pub/ruby/2.1/ruby-2.1.9.tar.gz | tar xz
Since GitLab 8.0, Git HTTP requests are handled by gitlab-workhorse (formerly gitlab-git-http-server). This is a small daemon written in Go. To install gitlab-workhorse we need a Go compiler.
yum install golang golang-bin golang-src
----------
## 3. System Users
## 4. System Users
Create a `git` user for Gitlab:
Loading
Loading
@@ -268,9 +266,9 @@ Save and exit.
----------
## 4. Database
## 5. Database
### 4.1 PostgreSQL (recommended)
### 5.1 PostgreSQL (recommended)
NOTE: because we need to make use of extensions we need at least pgsql 9.1 and the default 8.x on centos will not work. We need to get the PGDG repositories enabled
Loading
Loading
@@ -280,19 +278,11 @@ If there are any previous versions remove them:
template1=# CREATE EXTENSION IF NOT EXISTS pg_trgm;
template1=# \q
exit # exit uid=postgres, return to root
Loading
Loading
@@ -336,6 +326,20 @@ If you see the following:
your password has been accepted successfully and you can type \q to quit.
Check if the `pg_trgm` extension is enabled:
SELECT true AS enabled
FROM pg_available_extensions
WHERE name = 'pg_trgm'
AND installed_version IS NOT NULL;
If the extension is enabled this will produce the following output:
enabled
---------
t
(1 row)
Ensure you are using the right settings in your `/var/lib/pgsql/9.3/data/pg_hba.conf`
to not get ident issues (you can use trust over ident):
Loading
Loading
@@ -344,7 +348,13 @@ to not get ident issues (you can use trust over ident):
Check the official [documentation][psql-doc-auth] for more information on
authentication methods.
### 4.2 MySQL
### 5.2 MySQL
#### Note
We do not recommend using MySQL due to various issues. For example, case [(in)sensitivity](https://dev.mysql.com/doc/refman/5.0/en/case-sensitivity.html) and [problems](https://bugs.mysql.com/bug.php?id=65830) that [suggested](https://bugs.mysql.com/bug.php?id=50909)[fixes](https://bugs.mysql.com/bug.php?id=65830) [have](https://bugs.mysql.com/bug.php?id=63164).
#### MySQL
Install `mysql` and enable the `mysqld` service to start on boot:
Loading
Loading
@@ -380,7 +390,7 @@ Create the GitLab production database:
Grant the GitLab user necessary permissions on the table:
GRANT SELECT, LOCK TABLES, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER ON `gitlabhq_production`.* TO 'git'@'localhost';
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, CREATE TEMPORARY TABLES, DROP, INDEX, ALTER, LOCK TABLES, REFERENCES ON `gitlabhq_production`.* TO 'git'@'localhost';
Quit the database session:
Loading
Loading
@@ -397,7 +407,17 @@ Quit the database session:
----------
## 5. Redis
## 6. Redis
GitLab requires at least Redis 2.8.
Remove old version:
yum remove redis
Install new version from Remi's RPM repository:
yum --enablerepo=remi,remi-test install redis
Make sure redis is started on boot:
Loading
Loading
@@ -438,7 +458,7 @@ Add git to the redis group:
------
## 6. GitLab
## 7. GitLab
# We'll install GitLab into home directory of the user "git"
If you installed GitLab in another directory or as a user other than the default you should change these settings in `/etc/default/gitlab`. Do not edit `/etc/init.d/gitlab` as it will be
changed on upgrade.
Make GitLab start on boot:
Loading
Loading
@@ -604,31 +678,39 @@ Check if GitLab and its environment are configured correctly:
service gitlab start
## 7. Configure the web server
------
## 8. Configure the web server
Use either Nginx or Apache, not both. Official installation guide recommends nginx.
### Nginx
#### Installation
You will need a new version of nginx otherwise you might encounter an issue like [this][issue-nginx].
To do so, follow the instructions provided by the [nginx wiki][nginx-centos] and then install nginx with:
Make sure to edit the config file to match your setup:
# Change YOUR_SERVER_FQDN to the fully-qualified
# domain name of your host serving GitLab.
**Note:** If you want to use HTTPS, replace the `gitlab` Nginx config with `gitlab-ssl`. See [Using HTTPS](#using-https) for HTTPS configuration details.
Add `nginx` user to `git` group:
usermod -a -G git nginx
chmod g+rx /home/git/
Finally start nginx with:
service nginx start
#### Test Configuration
Validate your `gitlab` or `gitlab-ssl` Nginx config file with the following command:
Loading
Loading
@@ -637,10 +719,26 @@ Validate your `gitlab` or `gitlab-ssl` Nginx config file with the following comm
You should receive `syntax is okay` and `test is successful` messages. If you receive errors check your `gitlab` or `gitlab-ssl` Nginx config file for typos, etc. as indiciated in the error message given.
#### Restart
service nginx restart
### Apache
Httpd can be configured with or without SSL support. Please choose appropriate commands in next steps.
#### GitLab-Workhorse
Apache installation requires changes to gitlab-workhorse configuration. Change
`gitlab_workhorse_options` in `/etc/default/gitlab` to the following:
sed -i 's/logs\///g' /etc/httpd/conf.d/gitlab.conf
Open `/etc/httpd/conf.d/gitlab.conf` with your editor and replace `git.example.org` with your FQDN. Also make sure the path to your certificates is valid.
Open `/etc/httpd/conf.d/gitlab.conf` with your editor and replace `YOUR_SERVER_FQDN` with your FQDN. Also make sure the path to your certificates is valid.
Add `LoadModule ssl_module /etc/httpd/modules/mod_ssl.so` in `/etc/httpd/conf/httpd.conf`.
Now, the output will complain that your init script is not up-to-date as follows:
Init script up-to-date? ... no
Try fixing it:
Redownload the init script
For more information see:
doc/install/installation.md in section "Install Init Script"
Please fix the error above and rerun the checks.
Do not mind about that error if you are sure that you have downloaded the up-to-date file from https://gitlab.com/gitlab-org/gitlab-recipes/raw/master/init/sysvinit/centos/gitlab-unicorn and saved it to `/etc/init.d/gitlab`.
If all other items are green, then congratulations on successfully installing GitLab!
If all items are green, then congratulations on successfully installing GitLab!
**NOTE:** Supply `SANITIZE=true` environment variable to `gitlab:check` to omit project names from the output of the check command.
## Initial Login
Visit YOUR_SERVER in your web browser for your first GitLab login.
The setup has created an admin account for you. You can use it to log in:
If you didn't [provide a root password during setup](#initialize-database-and-activate-advanced-features),
you'll be redirected to a password reset screen to provide the password for the
initial administrator account. Enter your desired password and you'll be
redirected back to the login screen.
root
5iveL!fe
**Important Note:**
Please go over to your profile page and immediately change the password, so
nobody can access your GitLab by using this login information later on.
The default account's username is **root**. Provide the password you created
earlier and login. After login you can change the username if you wish.
**Enjoy!**
You can use `sudo service gitlab start` and `sudo service gitlab stop` to start and stop GitLab.
You can also check some [Advanced Setup Tips][tips].
## Links used in this guide
Loading
Loading
@@ -745,6 +834,7 @@ You can also check some [Advanced Setup Tips][tips].
