This page describes GitLab, which is a software for Git repository management and software development that can run on your own server.
Major GitLab features are depicted in this article on techdo.me.
- User management.
- SSH key management for accessing a repo via SSH and mapping to GUI user.
- Repository/project permissions (private, protected or public). Users and groups.
- View commits.
- Issue tracking.
- Markdown support.
- Branches and tags can be created in GUI.
- Merge requests. Code review.
- New files can be created and in the GUI.
- Files can be edited in the GUI.
- A wiki per project (in separate Git repo).
- Visualization of commits, branches, etc.
Access to repositories
The GitLab GUI always shows the links you need to use for accessing (cloning) the Git repositories either via HTTP or SSH.
Example URLs for project/repository:
SSH access on port 22:
- Note: The repo must be addressed with a absolute path (do not use ":" between hostname and pathname)
The corresponding clone commands are:
git clone http://gitlab.example.com/group1/project1.git git clone ssh://email@example.com/group1/project1.git
- For HTTP you need to authenticate with your GitLab user credentials, if it's not a public repo.
- It's recommended using SSH for accessing the repositories with a Git client.
- The SSH connect must go directly to the host GitLab has been installed on (no proxy in between).
- For SSH you need to always login as user git. The user mapping will be made via your SSH key(s).
- For SSH you need to authenticate with a SSH private key matching the public key you need to register in your GitLab user profile.
- The SSH keys must be unique. You can't add a public key to multiple user profiles. The keys are added to ~git/.ssh/authorized_keys.
- For SSH you need to take care using the correct SSH key, e.g. just add following to ~/.ssh/config:
Host gitlab.example.com IdentityFile ~/.ssh/id_rsa_emptypass StrictHostKeyChecking no UserKnownHostsFile /dev/null
- For SSH you can check the general SSH access and authentication by just connecting to the server with a native SSH client. In addition, your GitLab user mapping will be responded by the server as e.g. Welcome to GitLab, Peter Pan!. A successful connect (using SSH port forwarding) looks like:
> ssh firstname.lastname@example.org X11 forwarding request failed on channel 0 PTY allocation request failed on channel 0 Welcome to GitLab, Peter Pan! Connection to gitlab.example.com closed.
See Operations for info about installing and maintaining GitLab.
The GitLab GUI has an excellent online help available at
- GitLab Cookbook - Over 60 hands-on recipes to efficiently self-host your own Git repository using GitLab (PACKT Publishing)
GitLab official sites:
- GitLab Homepage
- GitLab Community Forum, see also this blog post.
- GitLab Community Edition
- GitLab Community Edition Documentation
- GitLab Community Edition Update
- GitLab Architecture Overview
- GitLab repository on GitLab
- GitLab repository on GitHub
- GitLab Flow
- Installing GitLab in your local network or your own PC and setting it up to work perfectly, with a guide to change SMTP settings
- Archlinux Wiki
- GitLab as an Alternative Development Platform for Github.com (LinuxCon Europe 2014)
Using under openSUSE: