Traducciones al Español
Estamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
Create a Linode account to try this guide with a $ credit.
This credit will be applied to any valid services used during your first  days.

Omnibus GitLab is a software package (or software stack) that allows you to easily install and run GitLab on your Linode. This guide walks you through the process of installing and setting up your own NGINX server on a typical Omnibus installation. Using the method outlined here, you are not forced to use Omnibus’s default settings, and can create as many virtual hosts as you need for hosting multiple websites and apps on the same server as your GitLab.

Preconfigured software stacks sometimes bring a series of challenges to those who need to customize specific settings. If you require more control over your installation, consider installing GitLab from source. This application stack could benefit from large amounts of disk space, so also consider using our Block Storage service with this setup.

Before You Begin

  1. Familiarize yourself with Linode’s Getting Started guide and complete the steps for setting your Linode’s hostname and timezone.

  2. Complete the sections of our Securing Your Server guide to create a standard user account, harden SSH access and remove unnecessary network services.

  3. This guide has been tested with Ubuntu 14.04 LTS and 16.04 LTS. Some commands will be slightly different for each version, so be sure to read each step carefully for version-specific instructions.

  4. Update your system:

    sudo apt-get update && sudo apt-get upgrade
This guide is written for a non-root user. Commands that require elevated privileges are prefixed with sudo. If you’re not familiar with the sudo command, visit our Users and Groups guide for more information.

Install Omnibus GitLab

If you’re already running an Omnibus GitLab environment upgrade to the newest version and proceed to the next section, Unbundle NGINX from Omnibus. If you’re installing GitLab for the first time, continue with the steps in this section.

Note that NGINX cannot be disabled in older versions of GitLab Community Edition (CE). If you currently have an older version of GitLab CE installed, we recommend that you upgrade incrementally to avoid issues.

  1. Install the dependencies:

    sudo apt-get install curl openssh-server ca-certificates postfix
  2. While installing Postfix, you’ll be asked to configure a few basic settings. On the first ncurses screen, select Internet Site as the mail configuration. On the second screen, enter your fully qualified domain name (FQDN). This will be used to send email to users when configuring new accounts and resetting passwords. The rest of the mail options will be configured automatically.

    Email restrictions on the Linode Platform
    In an effort to fight spam originating from our platform, outbound connections on ports 25, 465, and 587 are blocked by default on Compute Instances for some new accounts. These restrictions prevent applications from sending email. If you intend to send email from a Compute Instance, review the Send Email on the Linode Platform guide to learn more about our email policies and to request the removal of these restrictions.
  3. Add the GitLab CE repository and install the gitlab-ce package:

    curl -sS | sudo bash
    sudo apt-get install gitlab-ce

    You can view the contents of the script in its entirety on the GitLab website if you’re hesitant to run it sight-unseen. The GitLab downloads page also contains alternative download methods if you’re still not comfortable running their script.

Unbundle NGINX from Omnibus GitLab

  1. To unbundle NGINX from GitLab, we’ll need to disable the version included in the Omnibus package. Add the following lines to /etc/gitlab/gitlab.rb:

    File: /etc/gitlab/gitlab.rb
    # Unbundle NGINX from Omnibus GitLab
    nginx['enable'] = false
    # Set your NGINX's username
    web_server['external_users'] = ['www-data']
  2. Reconfigure GitLab to apply the changes:

    sudo gitlab-ctl reconfigure

For more information on how to customize Omnibus NGINX, visit the official NGINX documentation.

Install Ruby, Passenger, and NGINX

Now that GitLab’s bundled NGINX has been disabled, the next step is to install and configure the web server from scratch.

  1. Since GitLab is written in Ruby, install Ruby on your system:

    sudo apt-get install ruby
    sudo gem install rubygems-update
    sudo update_rubygems
  2. We’ll also need to install Phusion Passenger, a web application server for Ruby. Install Phusion Passenger’s PGP key:

    sudo apt-key adv --keyserver hkp:// --recv-keys 561F9B9CAC40B2F7
  3. Add Passenger’s APT repository by adding the following lines to /etc/apt/sources.list.d/passenger.list:

    File: /etc/apt/sources.list.d/passenger.list
    deb trusty main
    If you’re using Ubuntu 16.04, replace trusty with xenial in the above command.
  4. Update your package repositories:

    sudo apt-get update
  5. Install Passenger and NGINX:

    sudo apt-get install nginx-extras passenger
  6. Enable the new Passenger module by uncommenting the include /etc/nginx/passenger.conf; line from the /etc/nginx/nginx.conf file:

    File: /etc/nginx/nginx.conf
    include /etc/nginx/passenger.conf;
  7. Finally, restart NGINX. On Ubuntu 14.04:

    sudo service nginx restart

    On Ubuntu 16.04:

    sudo systemctl restart nginx

For further information, please refer to Installing Passenger + NGINX on Ubuntu 14.04 LTS (with APT).

Create a New Virtual Host

In this section, we’ll create a new virtual host to serve GitLab. Since we’ve unbundled NGINX, we’ll also be able to configure other virtual hosts for other websites and apps.

  1. Copy the default virtual host file to a new virtual host file, replacing with your virtual host:

    sudo cp /etc/nginx/sites-available/default /etc/nginx/sites-available/
  2. Edit your new virtual host file to match the following, replacing with your own hostname:

    File: /etc/nginx/sites-available/
    upstream gitlab {
        server unix:/var/opt/gitlab/gitlab-rails/sockets/gitlab.socket;
          server {
        listen 80;
        server_tokens off; # don't show the version number, a security best practice
        root /opt/gitlab/embedded/service/gitlab-rails/public;
        # Increase this if you want to upload large attachments
        # Or if you want to accept large git objects over http
        client_max_body_size 250m;
        # individual nginx logs for this gitlab vhost
        access_log  /var/log/nginx/gitlab_access.log;
        error_log   /var/log/nginx/gitlab_error.log;
        location / {
            proxy_redirect off;
            proxy_set_header Host $http_host;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_pass http://gitlab;
  3. Enable your new virtual host by symbolically linking it to sites-enabled (change

    sudo ln -s /etc/nginx/sites-available/ /etc/nginx/sites-enabled/
  4. Restart NGINX to load your changes. On Ubuntu 14.04:

    sudo service nginx restart

    On Ubuntu 16.04:

    sudo systemctl restart nginx
  5. Since NGINX needs to access GitLab, add the www-data user to the gitlab-www group:

    sudo usermod -aG gitlab-www www-data

Congratulations! You have turned a default Omnibus GitLab server into a multi-purpose one. To serve additional websites and apps using your newly unbundled NGINX server, simply create additional virtual hosts above, and configure them to your needs. For more information, please refer to our guide on how to configure NGINX.

More Information

You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.

This page was originally published on

Your Feedback Is Important

Let us know if this guide was helpful to you.

Join the conversation.
Read other comments or post your own below. Comments must be respectful, constructive, and relevant to the topic of the guide. Do not post external links or advertisements. Before posting, consider if your comment would be better addressed by contacting our Support team or asking on our Community Site.
The Disqus commenting system for Linode Docs requires the acceptance of Functional Cookies, which allow us to analyze site usage so we can measure and improve performance. To view and create comments for this article, please update your Cookie Preferences on this website and refresh this web page. Please note: You must have JavaScript enabled in your browser.