deac
/
gitlabhq
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Project management and code hosting application. Follow us on twitter @gitlabhq
4,442 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%
 
 
 
 
 
 
Go to file
Sebastian Ziebell 3374027e3a Merge branch 'master' into fixes/api, code clean up and tests fixed 
Conflicts:
	doc/api/projects.md
	spec/requests/api/projects_spec.rb
 		2013-03-07 14:51:56 +01:00
app Merge branch 'master' into fixes/api, code clean up and tests fixed 2013-03-07 14:51:56 +01:00
config Merge branch 'master' into fixes/api, code clean up and tests fixed 2013-03-07 14:51:56 +01:00
db Typo fixed 2013-03-05 14:29:44 +04:00
doc Merge branch 'master' into fixes/api, code clean up and tests fixed 2013-03-07 14:51:56 +01:00
features Adding sleep statements to allow sufficient time for the page to settle. 2013-03-06 16:36:11 +09:00
lib Merge branch 'master' into fixes/api, code clean up and tests fixed 2013-03-07 14:51:56 +01: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 Merge branch 'master' into fixes/api, code clean up and tests fixed 2013-03-07 14:51:56 +01: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
CONTRIBUTING.md Small fixes and better quoting. 2013-03-02 23:38:48 +01:00
Capfile.example Capistrano deployment example scripts 2013-02-20 00:13:18 -03:30
Gemfile Merge pull request #3158 from dosire/master 2013-03-06 10:22:45 -08:00
Gemfile.lock update Gemfile.lock with https rubygems 2013-03-06 21:10:01 +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
README.md Refactor README to split production/development environments 2013-03-06 20:06:56 -05:00
ROADMAP.md docs improvement 2013-02-28 18:30:07 +01:00
Rakefile init commit 2011-10-09 00:36:38 +03:00
VERSION It should be 5.0.0pre 2013-02-07 13:05:30 +02:00
config.ru added RAILS_RELATIVE_URL_ROOT support 2012-12-28 18:11:28 +00: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 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 10.000 organizations 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

For production

Follow the installation guide for production server.

For development

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 sandboxed and with all dependencies.

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

     sudo service gitlab start

or

    sudo /etc/init.d/gitlab restart

  1. Start it with Foreman in development mode

     bundle exec foreman start -p 3000

or start it manually

    bundle exec rails s
    bundle exec rake sidekiq:start

Running 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

      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