Project management and code hosting application. Follow us on twitter @gitlabhq
Go to file
Dmitriy Zaporozhets 7af16bbb0f Merge branch 'advanced-notes' of /home/git/repositories/gitlab/gitlabhq 2013-04-02 11:35:46 +00:00
app reset st_commits before setting new value to prevent error when old st_commits is broken 2013-04-02 11:32:41 +03:00
config Merge pull request #3396 from Andrew8xx8/issue-button-fix 2013-03-30 15:10:08 -07:00
db notification level for user 2013-03-26 10:48:07 +02:00
doc Adding special cases to the advanced setup notes. 2013-04-02 07:52:47 +02:00
features fix tabs features 2013-04-02 11:23:06 +03:00
lib Dont init repo on every create(:repo) 2013-04-01 17:27:44 +03:00
log init commit 2011-10-09 00:36:38 +03:00
public Add logo to deploy.html 2013-02-16 21:35:11 +02:00
script Fix sidekiq chech and added script/check 2013-01-09 20:31:05 +02:00
spec fix test 2013-04-02 14:30:32 +03:00
tmp Add tmp/.gitkeep file to ensure tmp folder exists on clone 2012-09-04 05:28:48 -04:00
vendor Result of misspellings run. 2013-03-17 19:46:54 +00:00
.foreman complete hooks for post receive 2012-01-08 13:20:20 +02:00
.gitignore Merge pull request #2990 from raphendyr/gitignore_and_logrotate 2013-02-18 10:01:09 -08:00
.rspec Spork support added 2013-03-26 13:38:42 +04:00
.simplecov organize simplecov 2013-01-07 22:23:13 +02:00
.travis.yml Update ruby to latest version. 2013-03-22 18:34:59 +01:00
CHANGELOG Update changelog 2013-03-25 16:12:12 +02:00 Improve header and wording. 2013-03-31 13:48:49 +02:00
Capfile.example Capistrano deployment example scripts 2013-02-20 00:13:18 -03:30
Gemfile use rollbacked version of grit to make gollum works 2013-03-30 16:35:19 +02:00
Gemfile.lock Fix therubyracer dependencies 2013-03-31 15:04:08 +03:00
Guardfile APi for commits. Better api docs 2012-09-21 13:22:30 +03:00
LICENSE init commit 2011-10-09 00:36:38 +03:00
Procfile Fix procfile and attachment in event nore 2013-02-11 19:25:06 +02:00 Removing duplication by putting everything in the readme. Allow us to close issues that deviate from the guidelines. 2013-03-30 11:35:35 +01:00 spelling error 2013-03-23 21:06:00 +01:00
Rakefile init commit 2011-10-09 00:36:38 +03:00
VERSION Updated changelog with transfer & security changes 2013-03-25 15:27:09 +02:00 added RAILS_RELATIVE_URL_ROOT support 2012-12-28 18:11:28 +00:00

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

  • build status (master branch)

  • build status (master branch)

  • Code Climate

  • Dependency Status

  • Coverage Status



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

** More details are in the requirements doc


Official production installation

Follow the installation guide for 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.

Unsupported production installation

New versions and upgrading

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

Getting started

  1. The Installation guide contains instructions to download an init script and run that on boot. With the init script you can also start GitLab

     sudo service gitlab start


    sudo /etc/init.d/gitlab restart
  1. Start it with Foreman in development mode

     bundle exec foreman start -p 3000

or start it manually

    bundle exec rails s
    bundle exec rake sidekiq:start

Running 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

Getting help

  • 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.

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

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

  • 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 without comment.

Getting in touch