Go to file
Yorick Peterse 4f3fa519c6 Use a UNION in MergeRequest.in_projects
The OR condition for source_project_id/target_project_id leads to a
query plan that performs rather poorly on PostgreSQL due to the use of
sub-queries. Because Rails offers no easy alternative for this
particular problem we're forced to using a UNION for both conditions.
The resulting query performs much faster than just using an OR.
2016-03-11 15:26:32 -05:00
app Use a UNION in MergeRequest.in_projects 2016-03-11 15:26:32 -05:00
bin
builds
config Disable Rubocop for PostgreSQL patches 2016-03-11 15:25:23 -05:00
db Updated schema to include Pg operator classes 2016-03-11 15:25:22 -05:00
doc Added pg_trgm to the PostgreSQL requirements 2016-03-11 15:25:24 -05:00
docker
features Merge branch 'group-activity-separate-tab' into 'master' 2016-03-11 19:58:10 +00:00
fixtures/emojis Update fixtures/emojis/aliases.json 2016-02-15 23:41:44 -05:00
lib Removed order from sub-query projects for search 2016-03-11 15:25:23 -05:00
log
public rewrite logo to simplify SVG code 2016-03-10 18:14:11 +01:00
scripts Retry bundler and apt-get 2016-03-09 21:22:25 +01:00
shared
spec Use a UNION in MergeRequest.in_projects 2016-03-11 15:26:32 -05:00
tmp
vendor/assets Fix #7959: Fix avatar stretching by providing a cropping feature 2016-02-09 22:26:50 +01:00
.flayignore
.foreman
.gitattributes
.gitignore Use dedicated relative_url.rb initializer 2016-02-29 21:17:48 +01:00
.gitlab-ci.yml Removed benchmark suite and its documentation 2016-03-10 11:15:43 +01:00
.hound.yml
.pkgr.yml
.rspec
.rubocop.yml
.ruby-version revert back to ruby 2.1 - use 2.1.8 2016-02-19 17:19:57 +01:00
.simplecov
.teatro.yml
CHANGELOG Added changelog entry for search performance 2016-03-11 15:26:32 -05:00
CONTRIBUTING.md No options please. 2016-03-04 18:23:55 -08:00
GITLAB_SHELL_VERSION
GITLAB_WORKHORSE_VERSION Use gitlab-workhorse 0.6.5 2016-02-17 14:20:49 +01:00
Gemfile Upgrade `omniauth-saml` to 1.5.0 and document it's new capabilities. 2016-03-10 16:07:10 -05:00
Gemfile.lock Merge branch 'omniauth-saml-upgrade' into 'master' 2016-03-11 16:48:52 +00:00
LICENSE
MAINTENANCE.md
PROCESS.md Fix wrong anchor in PROCESS.md 2016-03-02 11:00:32 +01:00
Procfile
README.md revert back to ruby 2.1 2016-02-19 15:59:46 +01:00
Rakefile Include relative url configuration in rake tasks 2016-02-29 21:17:48 +01:00
VERSION Update CHANGELOG and VERSION for 8.6.0-pre 2016-02-22 12:41:13 +01:00
config.ru Increase Unicorn memory limits to 300-350 2016-01-20 11:52:01 +01:00
doc_styleguide.md
docker-compose.yml

README.md

GitLab

build status Build Status Code Climate Coverage Status

Canonical source

The source of GitLab Community Edition is hosted on GitLab.com and there are mirrors to make contributing as easy as possible.

Open source software to collaborate on code

To see how GitLab looks please see the features page on our website.

  • 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 100,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

Editions

There are two editions of GitLab:

  • GitLab Community Edition (CE) is available freely under the MIT Expat license.
  • GitLab Enterprise Edition (EE) includes extra features that are more useful for organizations with more than 100 users. To use EE and get official support please become a subscriber.

Website

On about.gitlab.com you can find more information about:

Requirements

Please see the requirements documentation for system requirements and more information about the supported operating systems.

Installation

The recommended way to install GitLab is with the Omnibus packages on our package server. Compared to an installation from source, this is faster and less error prone. Just select your operating system, download the respective package (Debian or RPM) and install it using the system's package manager.

There are various other options to install GitLab, please refer to the installation page on the GitLab website for more information.

You can access a new installation with the login root and password 5iveL!fe, after login you are required to set a unique password.

Install a development environment

To work on GitLab itself, we recommend setting up your development environment with the GitLab Development Kit. If you do not use the GitLab Development Kit you need to install and setup all the dependencies yourself, this is a lot of work and error prone. One small thing you also have to do when installing it yourself is to copy the example development unicorn configuration file:

cp config/unicorn.rb.example.development config/unicorn.rb

Instructions on how to start GitLab and how to run the tests can be found in the development section of the GitLab Development Kit.

Software stack

GitLab is a Ruby on Rails application that runs on the following software:

  • Ubuntu/Debian/CentOS/RHEL
  • Ruby (MRI) 2.1
  • Git 1.7.10+
  • Redis 2.8+
  • MySQL or PostgreSQL

For more information please see the architecture documentation.

Third-party applications

There are a lot of third-party applications integrating with GitLab. These include GUI Git clients, mobile applications and API wrappers for various languages.

GitLab release cycle

For more information about the release process see the release documentation.

Upgrading

For upgrading information please see our update page.

Documentation

All documentation can be found on doc.gitlab.com/ce/.

Getting help

Please see Getting help for GitLab on our website for the many options to get help.

Is it any good?

Yes

Is it awesome?

Thanks for asking this question Joshua. These people seem to like it.