Find a file
Dmitriy Zaporozhets 7157f79caa
Refactor js behaviours helpers
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2014-03-11 15:15:08 +02:00
app Refactor js behaviours helpers 2014-03-11 15:15:08 +02:00
bin Added executable file permission to binstubs 2014-02-20 12:56:22 +01:00
config Add ldap check in application_controller and internal api 2014-03-10 17:10:23 +02:00
db Add User#last_credential_check_at 2014-03-11 10:07:22 +02:00
doc Use username instead of wierd email for first login 2014-03-11 12:18:14 +02:00
features Fixes a bug with group member administration 2014-03-10 22:56:26 -04:00
lib Merge branch 'master' of github.com:gitlabhq/gitlabhq 2014-03-11 11:29:18 +02:00
log init commit 2011-10-09 00:36:38 +03:00
public Truthful wording. Fixes #934 2014-02-04 11:39:07 +01:00
script Updated script/{web,background_job} to use #!/usr/bin/env bash rather than #!/bin/bash to allow for transparency between OS namely Linux and FreeBSD and for source installs of bash where path is not exported by default for /usr/local/{bin,sbin} 2014-02-10 09:51:51 -05:00
spec Merge branch 'simplify-emails-content' into 'master' 2014-03-11 10:39:29 +00:00
tmp Add tmp/.gitkeep file to ensure tmp folder exists on clone 2012-09-04 05:28:48 -04:00
vendor Use ace editor as gem 2014-02-10 16:18:46 +02:00
.foreman complete hooks for post receive 2012-01-08 13:20:20 +02:00
.gitignore Add envrc to git-ignore 2014-03-06 15:55:57 +01:00
.rspec Color in .rspec 2013-09-01 22:07:02 +03:00
.simplecov organize simplecov 2013-01-07 22:23:13 +02:00
.travis.yml Add jasmine tests to postgresql db 2014-02-23 14:30:06 +01:00
CHANGELOG More entries to CHANGELOG 2014-03-11 13:18:10 +02:00
config.ru Check specifically for Unicorn in rack config.ru file 2014-01-23 18:24:31 +01:00
CONTRIBUTING.md Add shell commands guide 2014-02-25 11:53:01 +01:00
Gemfile Add version_sorter gem 2014-03-09 00:01:06 -05:00
Gemfile.lock Add version_sorter gem 2014-03-09 00:01:06 -05:00
Guardfile APi for commits. Better api docs 2012-09-21 13:22:30 +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 Update references to gitlab dot com. 2014-03-10 17:40:40 +01:00
Procfile Cache MR diffs result. Improve diff output 2013-07-08 20:12:35 +03:00
Rakefile init commit 2011-10-09 00:36:38 +03:00
README.md Update references to gitlab dot com. 2014-03-10 17:40:40 +01:00
VERSION Its start for 6.7.0 2014-02-21 19:45:28 +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

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