deac/gitlabhq
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
Project management and code hosting application. Follow us on twitter @gitlabhq
4340 commits 6 branches 43 tags 25 MiB
Ruby 66.6%
HTML 19.7%
CSS 5.6%
Gherkin 3.2%
CoffeeScript 2.5%
Other 2.4%
Find a file
Dmitriy Zaporozhets 0c06b7fe20 Merge pull request #3106 from davidosomething/patch-1 
Update doc/install/databases.md
2013-03-05 06:52:41 -08:00
app Merge branch 'omniauth_no_email_1' of https://github.com/gliptak/gitlabhq into gliptak-omniauth_no_email_1 2013-03-05 16:48:18 +02:00
config Corrected some typos in gitlab.yml.example comments 2013-03-01 23:53:37 +01:00
db Typo fixed 2013-03-05 14:29:44 +04:00
doc Merge pull request #3106 from davidosomething/patch-1 2013-03-05 06:52:41 -08:00
features Merge pull request #3109 from hiroponz/improve-network-graph 2013-03-04 23:02:27 -08:00
lib Merge pull request #3143 from Undev/state-machine-3 2013-03-05 05:38:16 -08: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 fixed omniauth email spec 2013-03-05 16:50:37 +02:00
tmp Add tmp/.gitkeep file to ensure tmp folder exists on clone 2012-09-04 05:28:48 -04:00
vendor Move graph module from lib or vendor directory to app directory. 2013-02-26 20:31:39 +09: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 init commit 2011-10-09 00:36:38 +03:00
.simplecov organize simplecov 2013-01-07 22:23:13 +02:00
.travis.yml Update database cleaner. Remove postgres from travis build list since it gives us deadlocks always 2013-02-21 14:11:04 +02:00
CHANGELOG Add new entries to CHANGELOG 2013-02-21 17:01:02 +02:00
config.ru added RAILS_RELATIVE_URL_ROOT support 2012-12-28 18:11:28 +00:00
CONTRIBUTING.md Small fixes and better quoting. 2013-03-02 23:38:48 +01:00
Gemfile use grit_ext gem instead of fork 2013-03-04 08:56:54 +02:00
Gemfile.lock use grit_ext gem instead of fork 2013-03-04 08:56:54 +02: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
Rakefile init commit 2011-10-09 00:36:38 +03:00
README.md README code in lists 2013-03-03 18:22:56 +02:00
ROADMAP.md docs improvement 2013-02-28 18:30:07 +01:00
VERSION It should be 5.0.0pre 2013-02-07 13:05:30 +02:00

README.md

GitLab: self hosted Git management software

logo

GitLab allows you to

  • keep your code secure on your own server
  • manage repositories, users and access permissions
  • communicate though issues, line-comments and wiki's
  • perform code reviews with merge requests

GitLab is

  • powered by Ruby on Rails
  • completely free and open source (MIT license)
  • used by 10.000 organization to keep their code secure

Code status

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

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

  • Code Climate

  • Dependency Status

Resources

Requirements

  • Ubuntu/Debian*

  • ruby 1.9.3+

  • MySQL

  • git

  • gitlab-shell

  • redis

  • More details are in the requirements doc

Installation

You can either follow the "ordinary" Installation guide to install it on a machine or use the Vagrant virtual machine. The Installation guide is recommended to set up a production server. The Vargrant virtual machine is recommended for development since it makes it much easier to set up all the dependencies for integration testing.

Starting

  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 with:

     sudo service gitlab start

or

    sudo /etc/init.d/gitlab restart

  1. Start it with Foreman in development model

     bundle exec foreman start -p 3000

  2. Start it manually in development mode

     bundle exec rails s
 bundle exec rake sidekiq:start

Running the tests

  • Seed the database with

      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

Getting help

New versions and the API

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

Other documentation

Getting in touch