README.md

    GitLab: self hosted Git management software

    logo

    animated-screenshots

    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 more than 25.000 organizations to keep their code secure

    Code status

    • build status on ci.gitlab.org (master branch)

    • Code Climate

    • Dependency Status this button can be yellow (small updates are available) but must not be red (a security fix or an important update is available), gems are updated in major releases of GitLab.

    • Coverage Status

    Resources

    Requirements

    • Ubuntu/Debian**
    • ruby 1.9.3+
    • git 1.7.10+
    • redis 2.0+
    • MySQL or PostgreSQL

    ** More details are in the requirements doc

    Installation

    Official installation methods

    Third party one-click installers

    • Digital Ocean 1-Click Application Install Have a new server up in 55 seconds. Digital Ocean uses SSD disks which is great for an IO intensive app such as GitLab.

    • BitNami one-click installers This package contains both GitLab and GitLab CI. It is available as installer, virtual machine or for cloud hosting providers (Amazon Web Services/Azure/etc.).

    Unofficial installation methods

    • GitLab recipes repository with unofficial guides for using GitLab with different software (operating systems, webservers, etc.) than the official version.

    • Installation guides public wiki with unofficial guides to install GitLab on different operating systems.

    New versions and upgrading

    Since 2011 GitLab is released on the 22nd of every month. Every new release includes an upgrade guide.

    Run in production mode

    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

    Run in development mode

    Start it with Foreman

    bundle exec foreman start -p 3000

    or start each component separately

    bundle exec rails s
    script/background_jobs start

    Run 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 RAILS_ENV=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

    GitLab interfaces

    Getting help

    • Maintenance policy specifies what versions are supported.

    • Troubleshooting guide contains solutions to common problems.

    • Mailing list and Stack Overflow are the best places to ask questions. For example you can use it if you have questions about: permission denied errors, invisible repos, can't clone/pull/push or with web hooks that don't fire. Please search for similar issues before posting your own, there's a good chance somebody else had the same issue you have now and has resolved it. There are a lot of helpful GitLab users there who may be able to help you quickly. If your particular issue turns out to be a bug, it will find its way from there to a fix.

    • Feedback and suggestions forum is the place to propose and discuss new features for GitLab.

    • Contributing guide describes how to submit pull requests and issues. Pull requests and issues not in line with the guidelines in this document will be closed.

    • Support subscription connects you to the knowledge of GitLab experts that will resolve your issues and answer your questions.

    • Consultancy from the GitLab experts for installations, upgrades and customizations.

    • #gitlab IRC channel on Freenode to get in touch with other GitLab users and get help, it's managed by James Newton, Drew Blessing and Sam Gleske

    • Book written by GitLab enthusiast Jonathan M. Hethey is unofficial but it offers a good overview.

    Getting in touch

    项目简介

    gitlab project

    发行版本

    当前项目没有发行版本

    贡献者 18

    全部贡献者

    开发语言

    • Ruby 70.0 %
    • JavaScript 17.7 %
    • Vue 5.2 %
    • HTML 3.3 %
    • PLpgSQL 1.9 %