- 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
There are two editions of GitLab. GitLab Community Edition (CE) is available without any costs under an MIT license.
GitLab Enterprise Edition (EE) includes extra features that are most useful for organizations with more than 100 users. To get access to the EE and support please become a subscriber.
- The source of GitLab Community Edition is hosted on GitLab.com and there are mirrors to make contributing as easy as possible.
-
on ci.gitlab.org (master branch)
-
-
-
-
On about.gitlab.com you can find more information about:
- Subscriptions
- Consultancy
- Community
- Hosted GitLab.com use GitLab as a free service
- GitLab Enterprise Edition with additional features aimed at larger organizations.
- GitLab CI a continuous integration (CI) server that is easy to integrate with GitLab.
- Ubuntu/Debian/CentOS/RHEL**
- ruby 2.0+
- git 1.7.10+
- redis 2.0+
- MySQL or PostgreSQL
** More details are in the requirements doc.
Please see the installation page on the GitLab website for the various options.
Since a manual installation is a lot of work and error prone we strongly recommend the fast and reliable Omnibus package installation (deb/rpm).
You can access new installation with the login root and password 5iveL!fe, after login you are required to set a unique password.
There are a lot of applications and API wrappers for GitLab. Find them on our website.
Since 2011 a minor or major version of GitLab is released on the 22nd of every month. Patch and security releases come out when needed. New features are detailed on the blog and in the changelog. For more information about the release process see the release documentation. Features that will likely be in the next releases can be found on the feature request forum with the status started and completed.
For updating the the Omnibus installation please see the update documentation. For manual installations there is an upgrader script and there are upgrade guides.
We recommend setting up your development environment with the GitLab Development Kit. If you do not use the GitLab Development 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.
All documentation can be found on doc.gitlab.com/ce/.
Please see Getting help for GitLab on our website for the many options to get help.
Thanks for asking this question Joshua. These people seem to like it.