Find a file
2013-08-07 23:28:02 +03:00
app use control-group classes for inline forms in project new/edit pages 2013-08-07 23:28:02 +03:00
config Refactor recent branches page 2013-08-05 17:59:58 +03:00
db st_diff field for Note 2013-08-04 19:00:41 +03:00
doc added python api wrapper 2013-08-07 09:40:26 +02:00
features FIx wiki tests. Fixed margin for issues page 2013-08-02 12:15:30 +03:00
lib Fix edit files 2013-08-05 16:55:15 +03:00
log
public
script use git user in check script 2013-06-06 16:25:07 -05:00
spec Fix tests 2013-08-05 18:29:44 +03:00
tmp
vendor
.foreman
.gitignore move backup logic to lib. Fixed removing outdated backups 2013-08-05 12:26:33 +03:00
.rspec
.simplecov
.travis.yml rollback travis ruby1.9 version 2013-06-06 20:18:47 +03:00
CHANGELOG Fix typos 2013-07-29 12:47:06 +02:00
config.ru
CONTRIBUTING.md Merge branch 'rename-support-forum-to-mailing-list' of /home/git/repositories/gitlab/gitlabhq 2013-07-08 06:29:14 +00:00
Gemfile use rubygems for gitlab_git gem 2013-08-05 18:16:37 +03:00
Gemfile.lock use rubygems for gitlab_git gem 2013-08-05 18:16:37 +03:00
Guardfile
LICENSE
MAINTENANCE.md better wording encouraging usage of latest stable release in GitLab Maintenance Policy 2013-05-16 00:42:09 -07:00
Procfile Cache MR diffs result. Improve diff output 2013-07-08 20:12:35 +03:00
Rakefile
README.md Mention unofficial #gitlab IRC channel in README 2013-07-19 09:56:50 +02:00
VERSION 5.4.0 is rc1 2013-07-12 16:12:23 +03:00

GitLab: self hosted Git management software

logo

animated-screenshots

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 on ci.gitlab.org (master branch)

  • build status on travis-ci.org (master branch)

  • Code Climate

  • Dependency Status this button can be yellow (small updates are available) but must not be red (a security fix or an important update is available), gems are updated in major releases of GitLab.

  • Coverage Status

Resources

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

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 22nd a new version is released together with an upgrade guide.

Run in production mode

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

      All RSpec tests: bundle exec rake spec
    
      Single RSpec file: bundle exec rspec spec/controllers/commit_controller_spec.rb
    
  • Spinach integration tests

      All Spinach tests: bundle exec rake spinach
    
      Single Spinach test: bundle exec spinach features/project/issues/milestones.feature
    

GitLab interfaces

Getting help

  • Maintenance policy specifies what versions are supported.

  • Troubleshooting guide contains solutions to common problems.

  • Mailing list and Stack Overflow are the best places 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 has resolved it. 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.

  • Unofficial #gitlab IRC on Freenode is another way to get in touch with other GitLab users who may be able to help you.

  • 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