Difference between revisions of "GitLab Server"

From Worcester State University Computer Science Department Wiki
Jump to: navigation, search
(Created page with "Here's how we set up our GitLab server * The first step is installing CentOS ** GitLab recommends Ubuntu, so there's a few workarounds that need to be done for this. * We foll...")
 
Line 12: Line 12:
 
**** This fixes SELinux permissions so it'll use SSH keys.
 
**** This fixes SELinux permissions so it'll use SSH keys.
  
* known issues: https doesn't seem to work with a self-signed certificate
+
* known issues: https clone/push doesn't seem to work with a self-signed certificate

Revision as of 11:12, 22 November 2013

Here's how we set up our GitLab server

  • The first step is installing CentOS
    • GitLab recommends Ubuntu, so there's a few workarounds that need to be done for this.
  • We followed this guide: https://github.com/gitlabhq/gitlab-recipes/tree/7a1f1fc5ca089cdfb704008d4e1510280fe52af3/install/centos
    • Use nginx for the webserver
      • For nginx, edit the /etc/nginx/sites-enabled/gitlab you create and change all instances of git.example.com to git.cs.worcester.edu
      • modify /home/git/gitlab-shell/config.yml for https and enable self-signed cert and also edit /home/git/gitlab/config/gitlab.yml for https and port 443.
    • Fix SSH:
      • sudo usermod -U git
        • CentOS by default locks accounts without passwords, this unlocks it.
      • after logging in and adding an SSH key and run restorecon -R -v /home/git/.ssh
        • This fixes SELinux permissions so it'll use SSH keys.
  • known issues: https clone/push doesn't seem to work with a self-signed certificate