BigW Consortium Gitlab

installation.md 22.1 KB
Newer Older
1
# Installation from source
2

3 4
## Consider the Omnibus package installation

5
Since an installation from source is a lot of work and error prone we strongly recommend the fast and reliable [Omnibus package installation](https://about.gitlab.com/downloads/) (deb/rpm).
6

7 8 9 10 11 12
One reason the Omnibus package is more reliable is its use of Runit to restart any of the GitLab processes in case one crashes.
On heavily used GitLab instances the memory usage of the Sidekiq background worker will grow over time.
Omnibus packages solve this by [letting the Sidekiq terminate gracefully](http://doc.gitlab.com/ce/operations/sidekiq_memory_killer.html) if it uses too much memory.
After this termination Runit will detect Sidekiq is not running and will start it.
Since installations from source don't have Runit, Sidekiq can't be terminated and its memory usage will grow over time.

13 14
## Select Version to Install

15
Make sure you view [this installation guide](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md) from the tag (version) of GitLab you would like to install.
16 17
In most cases this should be the highest numbered production tag (without rc in it).
You can select the tag in the version dropdown in the top left corner of GitLab (below the menu bar).
18

19
If the highest number stable branch is unclear please check the [GitLab Blog](https://about.gitlab.com/blog/) for installation guide links by version.
20

21
## Important Notes
Valery Sizov committed
22

23 24
This guide is long because it covers many cases and includes all commands you need, this is [one of the few installation scripts that actually works out of the box](https://twitter.com/robinvdvleuten/status/424163226532986880).

25
This installation guide was created for and tested on **Debian/Ubuntu** operating systems. Please read [doc/install/requirements.md](./requirements.md) for hardware and operating system requirements. If you want to install on RHEL/CentOS we recommend using the [Omnibus packages](https://about.gitlab.com/downloads/).
26

27
This is the official installation guide to set up a production server. To set up a **development installation** or for many other installation options please see [the installation section of the readme](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/README.md#installation).
28

29
The following steps have been known to work. Please **use caution when you deviate** from this guide. Make sure you don't violate any assumptions GitLab makes about its environment. For example many people run into permission problems because they changed the location of directories or run services as the wrong user.
30

31 32 33
If you find a bug/error in this guide please **submit a merge request**
following the
[contributing guide](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md).
34

35
## Overview
Valery Sizov committed
36

37
The GitLab installation consists of setting up the following components:
38

39
1. Packages / Dependencies
40 41 42
1. Ruby
1. System Users
1. Database
43
1. Redis
44 45
1. GitLab
1. Nginx
Valery Sizov committed
46

47
## 1. Packages / Dependencies
Valery Sizov committed
48

49 50
`sudo` is not installed on Debian by default. Make sure your system is
up-to-date and install it.
51

52 53 54 55
    # run as root!
    apt-get update -y
    apt-get upgrade -y
    apt-get install sudo -y
Valery Sizov committed
56

57
**Note:** During this installation some files will need to be edited manually. If you are familiar with vim set it as default editor with the commands below. If you are not familiar with vim please skip this and keep using the default editor.
58

59
    # Install vim and set as default editor
60
    sudo apt-get install -y vim
61
    sudo update-alternatives --set editor /usr/bin/vim.basic
62

dosire committed
63
Install the required packages (needed to compile Ruby and native extensions to Ruby gems):
64

65 66 67 68 69 70
    sudo apt-get install -y build-essential zlib1g-dev libyaml-dev libssl-dev libgdbm-dev libreadline-dev libncurses5-dev libffi-dev curl openssh-server redis-server checkinstall libxml2-dev libxslt-dev libcurl4-openssl-dev libicu-dev logrotate python-docutils pkg-config cmake nodejs

If you want to use Kerberos for user authentication, then install libkrb5-dev:

    sudo apt-get install libkrb5-dev

71
**Note:** If you don't know what Kerberos is, you can assume you don't need it.
72

73 74 75 76 77
Make sure you have the right version of Git installed

    # Install Git
    sudo apt-get install -y git-core

78
    # Make sure Git is version 1.7.10 or higher, for example 1.7.12 or 2.0.0
79 80
    git --version

81
Is the system packaged Git too old? Remove it and compile from source.
82 83 84 85 86

    # Remove packaged Git
    sudo apt-get remove git-core

    # Install dependencies
87
    sudo apt-get install -y libcurl4-openssl-dev libexpat1-dev gettext libz-dev libssl-dev build-essential
88 89 90

    # Download and compile from source
    cd /tmp
Jacob Vosmaer committed
91 92
    curl -L --progress https://www.kernel.org/pub/software/scm/git/git-2.4.3.tar.gz | tar xz
    cd git-2.4.3/
Ben Bodenmiller committed
93
    ./configure
94 95 96 97 98
    make prefix=/usr/local all

    # Install into /usr/local/bin
    sudo make prefix=/usr/local install

99
    # When editing config/gitlab.yml (Step 5), change the git -> bin_path to /usr/local/bin/git
100

Sytse Sijbrandij committed
101
**Note:** In order to receive mail notifications, make sure to install a mail server. By default, Debian is shipped with exim4 but this [has problems](https://github.com/gitlabhq/gitlabhq/issues/4866#issuecomment-32726573) while Ubuntu does not ship with one. The recommended mail server is postfix and you can install it with:
102

103
    sudo apt-get install -y postfix
104 105

Then select 'Internet Site' and press enter to confirm the hostname.
106

107
## 2. Ruby
Valery Sizov committed
108

109
The use of Ruby version managers such as [RVM](https://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. For example, GitLab Shell is called from OpenSSH and having a version manager can prevent pushing and pulling over SSH. Version managers are not supported and we strongly advise everyone to follow the instructions below to use a system Ruby.
dosire committed
110

111
Remove the old Ruby 1.8 if present
112

113
    sudo apt-get remove ruby1.8
114

115
Download Ruby and compile it:
116

117
    mkdir /tmp/ruby && cd /tmp/ruby
118 119 120
    curl -O --progress https://cache.ruby-lang.org/pub/ruby/2.1/ruby-2.1.7.tar.gz
    echo 'e2e195a4a58133e3ad33b955c829bb536fa3c075  ruby-2.1.7.tar.gz' | shasum -c - && tar xzf ruby-2.1.7.tar.gz
    cd ruby-2.1.7
121
    ./configure --disable-install-rdoc
Valery Sizov committed
122 123 124
    make
    sudo make install

125 126
Install the Bundler Gem:

127
    sudo gem install bundler --no-ri --no-rdoc
128

129 130
## 3. Go

131 132 133 134
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. The instructions below assume you
use 64-bit Linux. You can find downloads for other platforms at the [Go download
135
page](https://golang.org/dl).
136

137 138 139
    curl -O --progress https://storage.googleapis.com/golang/go1.5.1.linux-amd64.tar.gz
    echo '46eecd290d8803887dec718c691cc243f2175fe0  go1.5.1.linux-amd64.tar.gz' | shasum -c - && \
      sudo tar -C /usr/local -xzf go1.5.1.linux-amd64.tar.gz
140
    sudo ln -sf /usr/local/go/bin/{go,godoc,gofmt} /usr/local/bin/
141
    rm go1.5.1.linux-amd64.tar.gz
142 143

## 4. System Users
144

145
Create a `git` user for GitLab:
146

147
    sudo adduser --disabled-login --gecos 'GitLab' git
Valery Sizov committed
148

149
## 5. Database
randx committed
150

151
We recommend using a PostgreSQL database. For MySQL check [MySQL setup guide](database_mysql.md). *Note*: because we need to make use of extensions you need at least pgsql 9.1.
152 153

    # Install the database packages
154
    sudo apt-get install -y postgresql postgresql-client libpq-dev
155 156 157 158

    # Login to PostgreSQL
    sudo -u postgres psql -d template1

159 160
    # Create a user for GitLab
    # Do not type the 'template1=#', this is part of the prompt
161
    template1=# CREATE USER git CREATEDB;
162 163 164 165 166 167 168 169 170

    # Create the GitLab production database & grant all privileges on database
    template1=# CREATE DATABASE gitlabhq_production OWNER git;

    # Quit the database session
    template1=# \q

    # Try connecting to the new database with the new user
    sudo -u git -H psql -d gitlabhq_production
171

172 173
    # Quit the database session
    gitlabhq_production> \q
randx committed
174

175
## 6. Redis
176 177 178 179 180

    sudo apt-get install redis-server

    # Configure redis to use sockets
    sudo cp /etc/redis/redis.conf /etc/redis/redis.conf.orig
181

182 183 184 185 186
    # Disable Redis listening on TCP by setting 'port' to 0
    sed 's/^port .*/port 0/' /etc/redis/redis.conf.orig | sudo tee /etc/redis/redis.conf

    # Enable Redis socket for default Debian / Ubuntu path
    echo 'unixsocket /var/run/redis/redis.sock' | sudo tee -a /etc/redis/redis.conf
Hugo Osvaldo Barrera committed
187 188 189 190 191 192 193 194 195 196 197
    # Grant permission to the socket to all members of the redis group
    echo 'unixsocketperm 770' | sudo tee -a /etc/redis/redis.conf

    # Create the directory which contains the socket
    mkdir /var/run/redis
    chown redis:redis /var/run/redis
    chmod 755 /var/run/redis
    # Persist the directory which contains the socket, if applicable
    if [ -d /etc/tmpfiles.d ]; then
      echo 'd  /var/run/redis  0755  redis  redis  10d  -' | sudo tee -a /etc/tmpfiles.d/redis.conf
    fi
198 199 200 201 202 203 204

    # Activate the changes to redis.conf
    sudo service redis-server restart

    # Add git to the redis group
    sudo usermod -aG redis git

205
## 7. GitLab
Valery Sizov committed
206

207 208
    # We'll install GitLab into home directory of the user "git"
    cd /home/git
209

210
### Clone the Source
randx committed
211

212
    # Clone GitLab repository
213
    sudo -u git -H git clone https://gitlab.com/gitlab-org/gitlab-ce.git -b 8-2-stable gitlab
Dmitriy Zaporozhets committed
214

215
**Note:** You can change `8-2-stable` to `master` if you want the *bleeding edge* version, but never install master on a production server!
216

Ben Bodenmiller committed
217
### Configure It
randx committed
218

219
    # Go to GitLab installation folder
220
    cd /home/git/gitlab
221

222
    # Copy the example GitLab config
223
    sudo -u git -H cp config/gitlab.yml.example config/gitlab.yml
Valery Sizov committed
224

225
    # Update GitLab config file, follow the directions at top of file
226
    sudo -u git -H editor config/gitlab.yml
227

228 229 230
    # Copy the example secrets file
    sudo -u git -H cp config/secrets.yml.example config/secrets.yml
    sudo -u git -H chmod 0600 config/secrets.yml
231

232
    # Make sure GitLab can write to the log/ and tmp/ directories
233 234
    sudo chown -R git log/
    sudo chown -R git tmp/
235
    sudo chmod -R u+rwX,go-w log/
236
    sudo chmod -R u+rwX tmp/
237

238 239 240
    # Make sure GitLab can write to the tmp/pids/ and tmp/sockets/ directories
    sudo chmod -R u+rwX tmp/pids/
    sudo chmod -R u+rwX tmp/sockets/
241

242
    # Make sure GitLab can write to the public/uploads/ directory
243
    sudo chmod -R u+rwX  public/uploads
244

245 246
    # Change the permissions of the directory where CI build traces are stored
    sudo chmod -R u+rwX builds/
247

248 249 250
    # Change the permissions of the directory where CI artifacts are stored
    sudo chmod -R u+rwX shared/artifacts/

251
    # Copy the example Unicorn config
252
    sudo -u git -H cp config/unicorn.rb.example config/unicorn.rb
Andrey Kumanyaev committed
253

254 255
    # Find number of cores
    nproc
256

257
    # Enable cluster mode if you expect to have a high load instance
258
    # Set the number of workers to at least the number of cores
259
    # Ex. change amount of workers to 3 for 2GB RAM server
Lukas Elmer committed
260
    sudo -u git -H editor config/unicorn.rb
261

262 263 264
    # Copy the example Rack attack config
    sudo -u git -H cp config/initializers/rack_attack.rb.example config/initializers/rack_attack.rb

265 266 267
    # Configure Git global settings for git user, used when editing via web editor
    sudo -u git -H git config --global core.autocrlf input

268 269 270
    # Configure Redis connection settings
    sudo -u git -H cp config/resque.yml.example config/resque.yml

271
    # Change the Redis socket path if you are not using the default Debian / Ubuntu configuration
272 273
    sudo -u git -H editor config/resque.yml

274
**Important Note:** Make sure to edit both `gitlab.yml` and `unicorn.rb` to match your setup.
275

276 277
**Note:** If you want to use HTTPS, see [Using HTTPS](#using-https) for the additional steps.

Ben Bodenmiller committed
278
### Configure GitLab DB Settings
279

280
    # PostgreSQL only:
281
    sudo -u git cp config/database.yml.postgresql config/database.yml
282

283 284 285
    # MySQL only:
    sudo -u git cp config/database.yml.mysql config/database.yml

286
    # MySQL and remote PostgreSQL only:
287
    # Update username/password in config/database.yml.
288
    # You only need to adapt the production settings (first part).
289
    # If you followed the database guide then please do as follows:
290 291
    # Change 'secure password' with the value you have given to $password
    # You can keep the double quotes around the password
292
    sudo -u git -H editor config/database.yml
293

294
    # PostgreSQL and MySQL:
295 296
    # Make config/database.yml readable to git only
    sudo -u git -H chmod o-rwx config/database.yml
297

298
### Install Gems
299

300
**Note:** As of bundler 1.5.2, you can invoke `bundle install -jN` (where `N` the number of your processor cores) and enjoy the parallel gems installation with measurable difference in completion time (~60% faster). Check the number of your cores with `nproc`. For more information check this [post](https://robots.thoughtbot.com/parallel-gem-installing-using-bundler). First make sure you have bundler >= 1.5.2 (run `bundle -v`) as it addresses some [issues](https://devcenter.heroku.com/changelog-items/411) that were [fixed](https://github.com/bundler/bundler/pull/2817) in 1.5.2.
301

302
    # For PostgreSQL (note, the option says "without ... mysql")
303
    sudo -u git -H bundle install --deployment --without development test mysql aws kerberos
304

305
    # Or if you use MySQL (note, the option says "without ... postgres")
306 307 308
    sudo -u git -H bundle install --deployment --without development test postgres aws kerberos

**Note:** If you want to use Kerberos for user authentication, then omit `kerberos` in the `--without` option above.
309

Ben Bodenmiller committed
310
### Install GitLab Shell
311

312
GitLab Shell is an SSH access and repository management software developed specially for GitLab.
313 314

    # Run the installation task for gitlab-shell (replace `REDIS_URL` if needed):
315
    sudo -u git -H bundle exec rake gitlab:shell:install[v2.6.7] REDIS_URL=unix:/var/run/redis/redis.sock RAILS_ENV=production
316

317
    # By default, the gitlab-shell config is generated from your main GitLab config.
318
    # You can review (and modify) the gitlab-shell config as follows:
319
    sudo -u git -H editor /home/git/gitlab-shell/config.yml
320

321
**Note:** If you want to use HTTPS, see [Using HTTPS](#using-https) for the additional steps.
322

323
**Note:** Make sure your hostname can be resolved on the machine itself by either a proper DNS record or an additional line in /etc/hosts ("127.0.0.1  hostname"). This might be necessary for example if you set up GitLab behind a reverse proxy. If the hostname cannot be resolved, the final installation check will fail with "Check GitLab API access: FAILED. code: 401" and pushing commits will be rejected with "[remote rejected] master -> master (hook declined)".
324

325
### Install gitlab-workhorse
326 327

    cd /home/git
328 329
    sudo -u git -H git clone https://gitlab.com/gitlab-org/gitlab-workhorse.git
    cd gitlab-workhorse
330
    sudo -u git -H git checkout 0.4.2
331 332
    sudo -u git -H make

333
### Initialize Database and Activate Advanced Features
334

335
    # Go to GitLab installation folder
336

mutec committed
337
    cd /home/git/gitlab
338 339 340 341 342 343 344

    sudo -u git -H bundle exec rake gitlab:setup RAILS_ENV=production

    # Type 'yes' to create the database tables.

    # When done you see 'Administrator account created:'

345
**Note:** You can set the Administrator/root password by supplying it in environmental variable `GITLAB_ROOT_PASSWORD` as seen below. If you don't set the password (and it is set to the default one) please wait with exposing GitLab to the public internet until the installation is done and you've logged into the server the first time. During the first login you'll be forced to change the default password.
346

347
    sudo -u git -H bundle exec rake gitlab:setup RAILS_ENV=production GITLAB_ROOT_PASSWORD=yourpassword
348

349 350 351 352 353 354
### Secure secrets.yml

The `secrets.yml` file stores encryption keys for sessions and secure variables.
Backup `secrets.yml` someplace safe, but don't store it in the same place as your database backups.
Otherwise your secrets are exposed if one of your backups is compromised.

355
### Install Init Script
356

Ben Bodenmiller committed
357
Download the init script (will be `/etc/init.d/gitlab`):
358

359
    sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
360 361 362 363

And if you are installing with a non-default folder or user copy and edit the defaults file:

    sudo cp lib/support/init.d/gitlab.default.example /etc/default/gitlab
364

Ben Bodenmiller committed
365
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.
366 367 368 369 370

Make GitLab start on boot:

    sudo update-rc.d gitlab defaults 21

371
### Setup Logrotate
372 373

    sudo cp lib/support/logrotate/gitlab /etc/logrotate.d/gitlab
374

375
### Check Application Status
376

377
Check if GitLab and its environment are configured correctly:
378

379
    sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
380

381
### Compile Assets
382 383 384

    sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production

385
### Start Your GitLab Instance
386 387 388 389 390

    sudo service gitlab start
    # or
    sudo /etc/init.d/gitlab restart

391
## 8. Nginx
Valery Sizov committed
392

393
**Note:** Nginx is the officially supported web server for GitLab. If you cannot or do not want to use Nginx as your web server, have a look at the [GitLab recipes](https://gitlab.com/gitlab-org/gitlab-recipes/).
394

395
### Installation
396

397
    sudo apt-get install -y nginx
398

399
### Site Configuration
400

401
Copy the example site config:
402

403
    sudo cp lib/support/nginx/gitlab /etc/nginx/sites-available/gitlab
404
    sudo ln -s /etc/nginx/sites-available/gitlab /etc/nginx/sites-enabled/gitlab
Valery Sizov committed
405

406 407
Make sure to edit the config file to match your setup:

408 409
    # Change YOUR_SERVER_FQDN to the fully-qualified
    # domain name of your host serving GitLab.
410 411
    # If using Ubuntu default nginx install:
    # either remove the default_server from the listen line
412
    # or else sudo rm -f /etc/nginx/sites-enabled/default
413
    sudo editor /etc/nginx/sites-available/gitlab
Dmitriy Zaporozhets committed
414

415
**Note:** If you want to use HTTPS, replace the `gitlab` Nginx config with `gitlab-ssl`. See [Using HTTPS](#using-https) for HTTPS configuration details.
Ben Bodenmiller committed
416 417 418 419 420 421

### Test Configuration

Validate your `gitlab` or `gitlab-ssl` Nginx config file with the following command:

    sudo nginx -t
422

423
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 indicated in the error message given.
424

425
### Restart
426

427
    sudo service nginx restart
Dmitriy Zaporozhets committed
428

429
## Done!
430

431
### Double-check Application Status
432 433 434 435 436 437 438

To make sure you didn't miss anything run a more thorough check with:

    sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production

If all items are green, then congratulations on successfully installing GitLab!

439 440
NOTE: Supply `SANITIZE=true` environment variable to `gitlab:check` to omit project names from the output of the check command.

441
### Initial Login
442

443
Visit YOUR_SERVER in your web browser for your first GitLab login. The setup has created a default admin account for you. You can use it to log in:
Valery Sizov committed
444

445
    root
446
    5iveL!fe
447

448
**Important Note:** On login you'll be prompted to change the password.
449 450 451

**Enjoy!**

452 453
You can use `sudo service gitlab start` and `sudo service gitlab stop` to start and stop GitLab.

454
## Advanced Setup Tips
Valery Sizov committed
455

456 457
### Using HTTPS

458 459 460 461 462 463 464 465 466 467 468 469 470 471 472
To use GitLab with HTTPS:

1. In `gitlab.yml`:
    1. Set the `port` option in section 1 to `443`.
    1. Set the `https` option in section 1 to `true`.
1. In the `config.yml` of gitlab-shell:
    1. Set `gitlab_url` option to the HTTPS endpoint of GitLab (e.g. `https://git.example.com`).
    1. Set the certificates using either the `ca_file` or `ca_path` option.
1. Use the `gitlab-ssl` Nginx example config instead of the `gitlab` config.
    1. Update `YOUR_SERVER_FQDN`.
    1. Update `ssl_certificate` and `ssl_certificate_key`.
    1. Review the configuration file and consider applying other security and performance enhancing features.

Using a self-signed certificate is discouraged but if you must use it follow the normal directions then:

Ben Bodenmiller committed
473
1. Generate a self-signed SSL certificate:
474

Ben Bodenmiller committed
475 476 477 478 479 480 481
    ```
    mkdir -p /etc/nginx/ssl/
    cd /etc/nginx/ssl/
    sudo openssl req -newkey rsa:2048 -x509 -nodes -days 3560 -out gitlab.crt -keyout gitlab.key
    sudo chmod o-r gitlab.key
    ```
1. In the `config.yml` of gitlab-shell set `self_signed_cert` to `true`.
482

483
### Enable Reply by email
Valery Sizov committed
484

485 486 487 488 489 490 491 492 493 494 495 496 497
See the ["Reply by email" documentation](../incoming_email/README.md) for more information on how to set this up.

### LDAP Authentication

You can configure LDAP authentication in `config/gitlab.yml`. Please restart GitLab after editing this file.

### Using Custom Omniauth Providers

See the [omniauth integration document](../integration/omniauth.md)

### Build your projects

GitLab can build your projects. To enable that feature you need GitLab Runners to do that for you.
Robert Schilling committed
498
Checkout the [GitLab Runner section](https://about.gitlab.com/gitlab-ci/#gitlab-runner) to install it
499

500
### Custom Redis Connection
501

502
If you'd like Resque to connect to a Redis server on a non-standard port or on a different host, you can configure its connection string via the `config/resque.yml` file.
503

504
    # example
505
    production: redis://redis.example.tld:6379
506

507
If you want to connect the Redis server via socket, then use the "unix:" URL scheme and the path to the Redis socket file in the `config/resque.yml` file.
508 509 510 511

    # example
    production: unix:/path/to/redis/socket

512
### Custom SSH Connection
513

514
If you are running SSH on a non-standard port, you must change the GitLab user's SSH config.
515

516
    # Add to /home/git/.ssh/config
517 518 519 520
    host localhost          # Give your setup a name (here: override localhost)
        user git            # Your remote git user
        port 2222           # Your port number
        hostname 127.0.0.1; # Your server name or IP
521

522
You also need to change the corresponding options (e.g. `ssh_user`, `ssh_host`, `admin_uri`) in the `config\gitlab.yml` file.
523

524
### Additional Markup Styles
525

526
Apart from the always supported markdown style there are other rich text files that GitLab can display. But you might have to install a dependency to do so. Please see the [github-markup gem readme](https://github.com/gitlabhq/markup#markups) for more information.
527 528 529 530 531 532

## Troubleshooting

### "You appear to have cloned an empty repository."

If you see this message when attempting to clone a repository hosted by GitLab,
533 534 535 536
this is likely due to an outdated Nginx or Apache configuration, or a missing or
misconfigured `gitlab-git-http-server` instance. Double-check that you've
[installed Go](#3-go), [installed gitlab-git-http-server](#install-gitlab-git-http-server),
and correctly [configured Nginx](#site-configuration).