GitLab: self hosted Git management software

GitLab allows you to

• keep your code secure on your own server
• manage repositories, users and access permissions
• communicate through issues, line-comments and wiki pages
• perform code review with merge requests

GitLab is

• powered by Ruby on Rails
• completely free and open source (MIT license)
• used by more than 10.000 organizations to keep their code secure

Code status

• on ci.gitlab.org (master branch)

• on travis-ci.org (master branch)

• 

• this button can be yellow (small updates are available) but must not be red (a security fix or an important update is available)

• 

Resources

• GitLab.org community site: Homepage Screenshots Blog Demo

• GitLab.com commercial services: Homepage Subscription Consultancy GitLab Cloud Blog

• GitLab CI: Readme of the GitLab open-source continuous integration server

Requirements

• Ubuntu/Debian**
• ruby 1.9.3
• MySQL or PostgreSQL
• git
• gitlab-shell
• redis

** More details are in the requirements doc

Installation

Official production installation

• Installation guide for a production server

Official development installation

If you want to contribute, please first read our Contributing Guidelines and then we suggest you to use the Vagrant virtual machine project to get an environment working with all dependencies.

• Vagrant virtual machine for development

Unsupported production installation

• GitLab recipes for setup on different platforms

• Unofficial installation guides

• BitNami one-click installers

• TurnKey Linux virtual appliance

New versions and upgrading

Each month on the 22nd a new version is released together with an upgrade guide.

• Upgrade guides

• Changelog

• Features that will be in the next release are listed on the feedback and suggestions forum with the status "started".

Run in production mode

1. The Installation guide contains instructions on how to download an init script and run it automatically on boot. You can also start the init script manually:

    sudo service gitlab start
   

or by directly calling the script

    sudo /etc/init.d/gitlab start

Run in development mode

Start it with Foreman

    bundle exec foreman start -p 3000

or start each component separately

    bundle exec rails s
    bundle exec rake sidekiq:start

Run the tests

• Seed the database

    bundle exec rake db:setup RAILS_ENV=test
    bundle exec rake db:seed_fu RAILS_ENV=test
  

• Run all tests

    bundle exec rake gitlab:test
  

• RSpec unit and functional tests

    bundle exec rake spec
  

• Spinach integration tests

    bundle exec rake spinach
  

GitLab interfaces

• GitLab API

• Rake tasks

• Directory structure

• Databases

Getting help

• Maintenance policy specifies what versions are supported.

• Troubleshooting guide contains solutions to common problems.

• Support forum is the best place to ask questions. For example you can use it if you have questions about: permission denied errors, invisible repos, can't clone/pull/push or with web hooks that don't fire. Please search for similar issues before posting your own, there's a good chance somebody else had the same issue you have now and had it resolved. There are a lot of helpful GitLab users there who may be able to help you quickly. If your particular issue turns out to be a bug, it will find its way from there to a fix.

• Feedback and suggestions forum is the place to propose and discuss new features for GitLab.

• Contributing guide describes how to submit pull requests and issues. Pull requests and issues not in line with the guidelines in this document will be closed.

• Support subscription connects you to the knowledge of GitLab experts that will resolve your issues and answer your questions.

• Consultancy allows you hire GitLab experts for installations, upgrades and customizations.

Getting in touch

• Core team

• Contributors

• Leader

• Contact page