Project management and code hosting application. Follow us on twitter @gitlabhq
 
 
 
 
 
 
Go to file
Dan Knox 8300ae366c Fix the Cancel button on the Edit Wiki page.
The Cancel button on the Edit Wiki page was still redirecting back
to the "Index" page which is no longer the default Wiki page.

This commit changes the Cancel button in the following ways:

  * Pressing Cancel while editing an existing Wiki page will now
    redirect you back to the latest version of that page.
  * Pressing Cancel while editing a brand new Wiki home page that
    does not yet exist will redirect you to back to the same Edit
    Wiki Home page.
2013-03-19 21:36:09 -07:00
app Fix the Cancel button on the Edit Wiki page. 2013-03-19 21:36:09 -07:00
config Comment external issue tracker by default in gitlab.yml.example 2013-03-19 15:11:31 +02:00
db Move snippets to own tab as feature. Make it disabled for new projects by default 2013-03-18 23:33:41 +02:00
doc API docs updated 2013-03-19 04:47:08 +00:00
features Fix the Cancel button on the Edit Wiki page. 2013-03-19 21:36:09 -07:00
lib Dont show blocked users in autocomplete 2013-03-19 18:07:14 +02: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 refactor emails a bit. Add email on ssh key creation 2013-03-19 20:00:41 +02:00
tmp Add tmp/.gitkeep file to ensure tmp folder exists on clone 2012-09-04 05:28:48 -04:00
vendor Result of misspellings run. 2013-03-17 19:46:54 +00: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 fixed travis env, added coverage badge 2013-03-10 20:29:34 +02:00
CHANGELOG 5.0 beta2 2013-03-19 19:17:59 +02:00
CONTRIBUTING.md Update links to GitLab.com after renaming of GitLab cloud. 2013-03-15 17:33:43 +01:00
Capfile.example Capistrano deployment example scripts 2013-02-20 00:13:18 -03:30
Gemfile rails up to 3.2.13 2013-03-19 18:52:17 +02:00
Gemfile.lock rails up to 3.2.13 2013-03-19 18:52:17 +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 Update links to GitLab.com after renaming of GitLab cloud. 2013-03-15 17:33:43 +01: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 5.0 beta2 2013-03-19 19:17:59 +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

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