Find a file
Dmitriy Zaporozhets 0004aafe37 Merge pull request #6473 from veonik/fix-readme-title
Fixed readme title
2014-03-06 10:21:41 +02:00
app Merge pull request #6473 from veonik/fix-readme-title 2014-03-06 10:21:41 +02:00
bin
config Replace backticks with Gitlab::Popen 2014-03-03 08:40:29 +01:00
db Add index_merge_request_diffs_on_merge_request_id 2014-03-04 10:38:09 +09:00
doc prioritise postgres in doc/update/patch_versions.md, assume postgres in doc/update/ruby.md 2014-03-04 00:40:30 +00:00
features Add tests to reopen MR 2014-03-03 10:21:50 +02:00
lib Merge branch 'shell_new_style' into 'master' 2014-03-05 10:45:46 +00:00
log
public Truthful wording. Fixes #934 2014-02-04 11:39:07 +01:00
script
spec Merge branch 'shell_new_style' into 'master' 2014-03-05 10:45:46 +00:00
tmp Add tmp/.gitkeep file to ensure tmp folder exists on clone 2012-09-04 05:28:48 -04:00
vendor
.foreman
.gitignore Add public assets to gitignore 2014-01-22 11:18:34 +02:00
.rspec
.simplecov
.travis.yml Add jasmine tests to postgresql db 2014-02-23 14:30:06 +01:00
CHANGELOG Added option to remove issue assignee on project issue page and issue edit page 2014-03-02 13:10:45 -05:00
config.ru
CONTRIBUTING.md
Gemfile Update gitlab_git to 5.7 2014-03-05 17:37:00 +02:00
Gemfile.lock Update gitlab_git to 5.7 2014-03-05 17:37:00 +02:00
Guardfile
LICENSE
MAINTENANCE.md Refer to release docs. 2014-02-19 13:12:55 +01:00
PROCESS.md
Procfile
Rakefile
README.md Add ruby to package. 2014-03-05 11:23:24 +01:00
VERSION

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

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

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

  • Contributing guide describes how to submit merge 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 from the GitLab experts for installations, upgrades and customizations.

  • #gitlab IRC channel on Freenode to get in touch with other GitLab users and get help, it's managed by James Newton (newton), Drew Blessing (dblessing), and Sam Gleske (sag47).

  • Book written by GitLab enthusiast Jonathan M. Hethey is unofficial but it offers a good overview.

  • Gitter chat room here you can ask questions when you need help.

Getting in touch