OS: Centos/Debian
So, anyone have any success running gitlab (http://gitlab.org/) + virtualmin together?
I managed to install gitlab on a Debian VPS the other day using the following guide (well combination of guides, but this being the base): https://github.com/gitlabhq/gitlabhq/blob/master/doc/install/installatio...
However, that guide relies on Nginx at the end to finally run the server part of it (Step 7 on that Guide). Would anyone have any idea about what i would/could to to get this running through virtualmin?
So going through the step 7 of that guide installing/configuring nginx
# Change YOUR_SERVER_FQDN to the fully-qualified
# domain name of your host serving GitLab.
sudo editor /etc/nginx/sites-available/gitlab
i notice on this file, it states the following:
# GITLAB
# Maintainer: @randx
# App Version: 5.0
upstream gitlab {
server unix:/home/git/gitlab/tmp/sockets/gitlab.socket;
}
server {
listen MY_SERVER_IP_ADDRESS:80 default_server; # e.g., listen 192.168.1.1:80;
server_name MY_GITLAB_SUBDOMAIN_NAME_FQDN; # e.g., server_name source.example.com;
root /home/git/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_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-Forwarded-Proto $scheme;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_pass http://gitlab;
}
}
so for sonversation sake, lets define MY_GITLAB_SUBDOMAIN_NAME_FQDN = gitlab.mydomain.com, and MY_SERVER_IP_ADDRESS = 1.2.3.4
i dont quite understand the following line in this file
root /home/git/gitlab/public;
Does that mean its the website root, or does it mean that is the website root and it needs to be accessed using root access?
Anyway, my main question was, if i follow through with the gitlab installation on my VPS (skip nginx step 7), and also install virtualmin on it, would i expect any conflicts/issues? And, knowing where the webroot of gitlab is from that above config file, can i simply add the gitlab.mydomain.com as a virtual server to my virtualmin and somehow point that specific virtual host to look at /home/git/gitlab/public ? If so, how would i do that, and what issues i might face later?
Thanks in advance :)