Find a file
Dmitriy Zaporozhets c4e81ed9de
Move update issue code to separate service
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2014-04-02 13:54:41 +03:00
app Move update issue code to separate service 2014-04-02 13:54:41 +03:00
bin Added executable file permission to binstubs 2014-02-20 12:56:22 +01:00
config Explain the default repository_downloads_path 2014-03-31 12:19:37 +02:00
db Start development Key seed id from 1. 2014-03-23 23:49:22 +01:00
doc Merge branch 'master' of github.com:gitlabhq/gitlabhq 2014-04-01 12:28:21 +03:00
features Fix tests 2014-03-25 12:05:37 +02:00
lib Move update issue code to separate service 2014-04-02 13:54:41 +03:00
log
public Truthful wording. Fixes #934 2014-02-04 11:39:07 +01:00
script Add load_ok to background_jobs usage message 2014-03-20 14:47:06 +01:00
spec Move update issue code to separate service 2014-04-02 13:54:41 +03:00
tmp
vendor Move images from vendor to app so they are compiled by rails 2014-03-12 10:19:24 +02:00
.foreman
.gitignore Add envrc to git-ignore 2014-03-06 15:55:57 +01:00
.rspec Remove --drb from .rspec 2014-03-24 08:55:27 -04:00
.simplecov organize simplecov 2013-01-07 22:23:13 +02:00
.travis.yml Fix travis setup 2014-03-18 22:21:25 -04:00
CHANGELOG Update changelog with new feature 2014-04-01 10:45:10 +03:00
config.ru Check specifically for Unicorn in rack config.ru file 2014-01-23 18:24:31 +01:00
CONTRIBUTING.md Updated contribution guidelines to specify MRs should be to master. 2014-03-27 14:09:50 -04:00
Gemfile Remove Spork 2014-03-24 08:55:27 -04:00
Gemfile.lock Remove Spork 2014-03-24 08:55:27 -04:00
Guardfile Use ruby 1.9 hash syntax in Guardfile 2014-04-01 13:08:16 +03:00
LICENSE update copyright year to range 2014-02-16 23:06:35 -08:00
MAINTENANCE.md Refer to release docs. 2014-02-19 13:12:55 +01:00
PROCESS.md Merge branch 'master' into define-feature-request 2014-03-25 20:57:21 +01:00
Procfile Use 2 workers in development 2014-03-20 10:16:17 +02:00
Rakefile
README.md Link to doc site from the readme. 2014-04-01 09:19:37 +02:00
VERSION Time for 6.8.0pre 2014-03-26 09:50:18 +02:00

GitLab: self hosted Git management software

logo

animated-screenshots

Gitlab is open source software to collaborate on code

  • Manage git repositories with fine grained access controls that keep your code secure
  • Perform code reviews and enhance collaboration with merge requests
  • Each project can also have an issue tracker and a wiki
  • Used by more than 50,000 organizations, GitLab is the most popular solution to manage git repositories on-premises
  • Completely free and open source (MIT Expat license)
  • Powered by Ruby on Rails

Code status

  • build status on ci.gitlab.org (master branch)

  • Code Climate

  • Coverage Status

Resources

Requirements

  • Ubuntu/Debian/CentOS/RHEL**
  • ruby 1.9.3+
  • git 1.7.10+
  • redis 2.0+
  • MySQL or PostgreSQL

** More details are in the requirements doc

Installation

Official installation methods

Third party one-click installers

Unofficial installation methods

  • GitLab recipes repository with unofficial guides for using GitLab with different software (operating systems, webservers, etc.) than the official version.

  • Installation guides public wiki with unofficial guides to install GitLab on different operating systems.

New versions and upgrading

Since 2011 GitLab is released on the 22nd of every month. Every new release includes an upgrade guide and new features are detailed in the Changelog.

It is recommended to follow a monthly upgrade schedule. Security releases come out when needed. For more information about the release process see the documentation for monthly and security releases.

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
script/background_jobs start

Run the tests

  • Run all tests

      bundle exec rake 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
    

Documentation

All documentation can be found on doc.gitlab.com/ce/.

Getting help

Please see Getting help for GitLab on our website for the many options to get help.