• 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

• 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 www.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.

Access GitLab from multiple platforms with applications below. These applications are maintained by contributors, GitLab B.V. does not offer support for them.

• iPhone app
• Android app
• Chrome app
• Command line client
• Ruby API wrapper

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

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.

The Installation guide contains instructions on how to download an init script and run it automatically on boot. You can also start the init script manually:

sudo service gitlab start

or by directly calling the script:

 sudo /etc/init.d/gitlab start

Please login with root / 5iveL!fe

We recommend setting up your development environment with the cookbook. If you do not use the cookbook you might need to copy the example development unicorn configuration file

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

Start it with Foreman

bundle exec foreman start -p 3000

or start each component separately:

bundle exec rails s
bin/background_jobs start

And surf to localhost:3000 and login with root / 5iveL!fe.

• Run all tests:

  bundle exec rake test
  

• RSpec unit and functional tests.

  All RSpec tests: bundle exec rake spec

  Single RSpec file: bundle exec rspec spec/controllers/commit_controller_spec.rb

• Spinach integration tests.

  All Spinach tests: bundle exec rake spinach

  Single Spinach test: bundle exec spinach features/project/issues/milestones.feature

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.

Yes

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