Revision 1 as of 2015-03-30 20:54:30

Clear message

[TPG] has set up a "GitLab" instance on a VM, running at https://gitlab.ucc.asn.au/

GitLab is a git repository manager, similar to GitHub, and looks to be a good replacement for gitosis+gitweb.

Setup

It's a VM on medico, with a relatively small HDD.

GitLab itself was installed from a .deb acquired from the GitLab website, which installs to /opt/gitlab. This was symlinked to /home/opt/gitlab (because / was a small partition).

GitLab has been configured (using the config file in /etc/gitlab/gitlab.rb) to store repositories in /home/gitlab-repositories, which (because I'm lazy) is a symlink to /services/gitlab. This is a mount of services:/services/gitlab (the VM is only allowed access to this subdir, safety first.)

Management

To start/restart/stop the GitLab service, use the gitlab-ctl tool. * gitlab-ctl start - Start the service * gitlab-ctl stop - Stop the service * gitlab-ctl reconfigure - Apply any configuration changes

Editing the display

I have done some minor patching to the GitLab code to customise the login page. This was done in the GitLab rails application directory : /home/opt/gitlab/embedded/service/gitlab-rails. This has been turned into a git repo to trace changes and upgrades.

To apply changes to the page templates, stopping+starting the services should suffice. If any images or CSS are changed, then you need to regenerate the assets by running the following command from the rails app root. RAILS_ENV=production PATH=/home/opt/gitlab/embedded/bin/:$PATH ./bin/bundle exec rake assets:precompile