Go to file
Brett Walker 54d88e0690 make sure there is a dependency on Gitlab::CurrentSettings is
This fixes an issue where the Rails autoload system would throw various `Unable to autoload constant` errors (such as `Unable to autoload constant EE::ProjectsHelper`) when using the autoload system (such with `spring` or `reload!` in the rails console.

This error was specifically ocurring in the EE code, however, it's seems reasonable to place the fix in CE as a general innoculation.
2018-02-09 18:08:33 +01:00
.github
.gitlab
app Merge branch 'fl-mr-widget-missing-branch' into 'master' 2018-02-09 12:14:20 +00:00
bin
builds
changelogs Update vue component naming guidelines 2018-02-08 21:20:54 +02:00
config make sure there is a dependency on Gitlab::CurrentSettings is 2018-02-09 18:08:33 +01:00
db Early migrations populating fork-networks: no-op 2018-02-08 09:44:58 +01:00
doc Merge branch 'docs/update-vue-naming-guidelines' into 'master' 2018-02-09 10:29:54 +00:00
docker
features Merge branch '42798-fix-hardcoded-id-in-spinach' into 'master' 2018-02-06 13:14:08 +00:00
fixtures/emojis
generator_templates
lib Remove allow_n_plus_1 from Git::Repository#branches_filter 2018-02-08 19:20:46 +01:00
locale Annotate charts page for internationalization 2018-02-08 05:55:52 +00:00
log
public
qa Merge branch 'qa/gb/do-not-require-test-network-in-pipeline-tests' into 'master' 2018-02-09 16:07:00 +00:00
rubocop
scripts
shared
spec Merge branch 'fl-mr-widget-missing-branch' into 'master' 2018-02-09 12:14:20 +00:00
symbol
tmp
vendor Merge branch '10-5-update-dependencies-license-list' into 'master' 2018-02-08 15:14:46 +00:00
.babelrc
.codeclimate.yml
.csscomb.json
.eslintignore
.eslintrc
.flayignore
.foreman
.gitignore
.gitlab-ci.yml Merge branch 'dz-sast-confidence-level' into 'master' 2018-02-05 10:10:37 +00:00
.haml-lint.yml
.mailmap
.nvmrc
.pkgr.yml
.rubocop.yml
.rubocop_todo.yml
.ruby-version
.scss-lint.yml
CHANGELOG.md Update CHANGELOG.md for 10.2.8 2018-02-07 10:14:14 -06:00
CONTRIBUTING.md
GITALY_SERVER_VERSION Update GITALY_SERVER_VERSION 2018-02-07 10:04:56 +00:00
GITLAB_PAGES_VERSION
GITLAB_SHELL_VERSION Bumps Gitlab Shell version to 6.0.3 2018-02-08 16:42:33 +00:00
GITLAB_WORKHORSE_VERSION Upgrade GitLab Workhorse to v3.6.0 2018-02-06 15:34:44 +01:00
Gemfile Merge branch 'pawel/use-released-prometheus-version' into 'master' 2018-02-08 00:40:33 +00:00
Gemfile.lock Merge branch 'pawel/use-released-prometheus-version' into 'master' 2018-02-08 00:40:33 +00:00
LICENSE
MAINTENANCE.md
PROCESS.md
Procfile
README.md
Rakefile
VERSION
config.ru
doc_styleguide.md
docker-compose.yml
package.json Restore feature_highlight code 2018-02-05 12:10:09 -06:00
yarn.lock Restore feature_highlight code 2018-02-05 12:10:09 -06:00

README.md

GitLab

Build status Overall test coverage Dependency Status Code Climate Core Infrastructure Initiative Best Practices Gitter

Test coverage

  • Ruby coverage Ruby
  • JavaScript coverage JavaScript

Canonical source

The canonical source of GitLab Community Edition is hosted on GitLab.com.

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
  • Complete continuous integration (CI) and CD pipelines to builds, test, and deploy your applications
  • Each project can also have an issue tracker, issue board, 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)

Hiring

We're hiring developers, support people, and production engineers all the time, please see our jobs page.

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.

Contributing

GitLab is an open source project and we are very happy to accept community contributions. Please refer to CONTRIBUTING.md for details.

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 getting started 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/OpenSUSE
  • Ruby (MRI) 2.3
  • Git 2.8.4+
  • Redis 2.8+
  • PostgreSQL (preferred) or MySQL

For more information please see the architecture documentation.

UX design

Please adhere to the UX Guide when creating designs and implementing code.

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