Comment configurer GitLab comme un sous-domaine dans nginix.conf

J'ai été en utilisant Apache2 avant j'ai installé GitLab sur mon VPS. Je veux juste faire GitLab un sous-domaine de mon site (git.example.com) et que mon site principal (www.example.com) regarder /var/www/html/index.html

Voici mon nginx.fichier conf dès maintenant:

user www-data;
worker_processes  1;

error_log  /var/log/nginx/error.log;
pid        /var/run/nginx.pid;

events {
    worker_connections  1024;
    # multi_accept on;
}

http {
    include       /etc/nginx/mime.types;

    access_log  /var/log/nginx/access.log;

    sendfile        on;
    #tcp_nopush     on;

    #keepalive_timeout  0;
    keepalive_timeout  65;
    tcp_nodelay        on;

    gzip  on;
    gzip_disable "MSIE [1-6]\.(?!.*SV1)";

    include /etc/nginx/conf.d/*.conf;
    include /etc/nginx/sites-enabled/*;

upstream gitlab {

    server unix:/home/gitlab/gitlab/tmp/sockets/gitlab.socket; }

    server {

        listen 80;
        server_name www.example.com;
        root /home/gitlab/gitlab/public;

        # individual nginx logs for this gitlab vhost
        access_log  /var/log/nginx/gitlab_access.log;
        error_log   /var/log/nginx/gitlab_error.log;

        location /{
            # serve static files from defined root folder;.
            # @gitlab is a named location for the upstream fallback, see below
            try_files $uri $uri/index.html $uri.html @gitlab;
        }

        # if a file, which is not found in the root folder is requested,
        # then the proxy pass the request to the upsteam (gitlab unicorn)
        location @gitlab {
            proxy_redirect     off;

            # you need to change this to "https", if you set "ssl" directive to "on"
            proxy_set_header   X-FORWARDED_PROTO http;
            proxy_set_header   Host              $http_host;
            proxy_set_header   X-Real-IP         $remote_addr;

            proxy_pass http://gitlab;
        }
    }

}

A cette question a été corrigé depuis? Veuillez signifier que la réponse est si nous pouvons compter sur une réponse... Merci!!!!

OriginalL'auteur mightcouldb1 | 2012-09-02

Voici ma configuration qui fonctionne sur un sous-domaine.

server {
  listen 80;
  server_name gitlab.example.com;
  root /home/gitlab/gitlab/public;

  # individual nginx logs for this gitlab vhost
  access_log  /var/log/nginx/gitlab_access.log;
  error_log   /var/log/nginx/gitlab_error.log;

  location / {
    # serve static files from defined root folder;.
    # @gitlab is a named location for the upstream fallback, see below
    try_files $uri $uri/index.html $uri.html @gitlab;
  }

  # if a file, which is not found in the root folder is requested, 
  # then the proxy pass the request to the upsteam (gitlab unicorn)
  location @gitlab {
    proxy_redirect     off;
    # you need to change this to "https", if you set "ssl" directive to "on"
    proxy_set_header   X-FORWARDED_PROTO http;
    proxy_set_header   Host              gitlab.example.com:80;
    proxy_set_header   X-Real-IP         $remote_addr;
    proxy_pass http://gitlab;
  }
}

Quelle est la version de gitlab cela fonctionne?
Il a travaillé pour gitlab 8.4.4

OriginalL'auteur Sonny Scroggin

Voici ce que j'ai fait, je ne sais pas si c'est optimal, mais il fonctionne.

nginx.conf:

events {
    worker_connections 1024;
}
http {
    include /etc/nginx/mime.types;
    root .;
    server {
          listen 80;
          server_name www.whatever.com whatever.com;
    }
    server {
          listen 80;
          server_name gitlab.whatever.com;
          location /{
               proxy_pass http://127.0.0.1:8000;
          }
     }
}

dans gitlab.rb, supprimez/modifiez cette ligne:

nginx['listen_port'] = 8000

OriginalL'auteur Renaud

Vous aurez besoin de créer deux fichier vhost pour chacun des projets (Gitlab et votre site principal).

Dans votre Gitlab fichier vhost, vous pouvez utiliser le fichier par défaut, la modification de certains champs:

# GITLAB repository

upstream gitlab {
  server unix:/home/git/gitlab/tmp/sockets/gitlab.socket;
}

server {
    listen 80;                   # In most cases *:80 is a good idea
    server_name git.example.com; # E.g., server_name source.example.com;
    server_tokens off;           # don't show the version number, a security best practice

    root /home/git/gitlab/public;         # Where your repository is located
    index index.php index.html index.htm; # Extensions to look for

    # Logs for this gitlab vhost. If something goes wrong, check these files to figure out what is missing
    access_log /var/log/nginx/gitlab_access.log;
    error_log  /var/log/nginx/gitlab_error.log;

    location /{
        # serve static files from defined root folder;.
        # @gitlab is a named location for the upstream fallback, see below
        try_files $uri $uri/index.html $uri.html @gitlab;
    }

    # if is a file that could not be found in the root folder is requested,
    # then the proxy pass the request to the upsteam (gitlab unicorn)
    location @gitlab {
        proxy_read_timeout 300;    # https://github.com/gitlabhq/gitlabhq/issues/694
        proxy_connect_timeout 300; # https://github.com/gitlabhq/gitlabhq/issues/694
        proxy_redirect     off;

        proxy_set_header X-Forwared-Proto $scheme;
        proxy_set_header X-Real-IP        $remote_addr;
        proxy_set_header X-Forwarded-For  $remote_addr;
        proxy_set_header Host             git.example.org:80; # Host name for your Gitlab Project

        proxy_pass  http://gitlab; # Alias
    }
}

Ensuite, créez un lien symbolique dans /sites-enabled/dossier:

$ sudo rm /etc/nginx/sites-enabled/example
$ sudo ln -s /etc/nginx/sites-available/example /etc/nginx/sites-enabled/example

Redémarrer Nginx service nginx restart.

Si ne fonctionne toujours pas, vérifiez votre journal d'erreur à l'aide de tail -f /var/log/nginx/gitlab_error.log. Cela peut vous aider à comprendre ce que vous êtes absent.

Remarque:
Pour répondre à cette question, la version de PHP que j'ai utilisé était 5.3.10 et la Nginx version 1.1.19.

Références

Comment Configurer Nginx en tant que Reverse Proxy Apache -
https://www.digitalocean.com/community/tutorials/how-to-configure-nginx-as-a-reverse-proxy-for-apache

Queue de commande
http://en.wikipedia.org/wiki/Tail_%28Unix%29

OriginalL'auteur Matheus Santos

Vous devez vous connecter pour publier un commentaire.