kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
No description https://gitlab.com/gitlab-org/gitlab-foss
6566 commits 1 branch 0 tags 899 MiB
Ruby 69.2%
JavaScript 18.7%
Vue 6.6%
Haml 2%
HTML 1.3%
Other 2.2%
Find a file
Johannes Schleifenbaum b5d7bcb784 [gitlab:check] Fix detecting the status of sidekiq 
If you are running another sidekiq instance on your server, e.g. GitLab
CI, the check script would parse the output of `ps aux` searching for
`sidekiq` and returning success, although the GitLab sidekiq may not be
running.

Now the `ps` call will only print the processes run by the GitLab user.
2013-09-27 16:06:06 +02:00
app Merge branch 'patch-2' of https://github.com/zzet/gitlabhq into zzet-patch-2 2013-09-26 22:19:01 +03:00
config Public projects feature - step2 2013-09-24 22:14:28 +03:00
db Namespaces.owner_id can be null 2013-09-26 14:48:58 +03:00
doc Merge pull request #5146 from karlhungus/feature-api-search-for-projects-by-name 2013-09-25 06:57:34 -07:00
features rewrite issues search test to prevent ajax requests running after test 2013-09-27 16:25:24 +03:00
lib [gitlab:check] Fix detecting the status of sidekiq 2013-09-27 16:06:06 +02:00
log init commit 2011-10-09 00:36:38 +03:00
public Add logo to deploy.html 2013-02-16 21:35:11 +02:00
script use git user in check script 2013-06-06 16:25:07 -05:00
spec Remove issues search rspec since we test it with spinach too 2013-09-26 15:56:05 +03:00
tmp Add tmp/.gitkeep file to ensure tmp folder exists on clone 2012-09-04 05:28:48 -04:00
vendor bring more usability to issues filtering. Block issues area on loading filtered results 2013-05-08 13:43:21 +03:00
.foreman complete hooks for post receive 2012-01-08 13:20:20 +02:00
.gitignore Added .ruby-version & .ruby-gemset in .gitignore 2013-09-16 19:19:04 +05:30
.rspec Color in .rspec 2013-09-01 22:07:02 +03:00
.simplecov organize simplecov 2013-01-07 22:23:13 +02:00
.travis.yml Dont test 1.9 with travis 2013-09-26 19:22:04 +03:00
CHANGELOG Mention public projects in CHANGELOG 2013-09-25 15:49:35 +03:00
config.ru added RAILS_RELATIVE_URL_ROOT support 2012-12-28 18:11:28 +00:00
CONTRIBUTING.md Add information about the contributing process 2013-08-08 09:55:28 +02:00
Gemfile Update gitlab_git to version 2.3.1 2013-09-21 18:54:18 +02:00
Gemfile.lock Update gitlab_git to version 2.3.1 2013-09-21 18:54:18 +02:00
Guardfile APi for commits. Better api docs 2012-09-21 13:22:30 +03:00
LICENSE init commit 2011-10-09 00:36:38 +03:00
MAINTENANCE.md better wording encouraging usage of latest stable release in GitLab Maintenance Policy 2013-05-16 00:42:09 -07:00
PROCESS.md spelling mistake. 2013-09-04 09:08:39 +02:00
Procfile Cache MR diffs result. Improve diff output 2013-07-08 20:12:35 +03:00
Rakefile init commit 2011-10-09 00:36:38 +03:00
README.md README improved. Removed travis badge 2013-09-19 10:45:31 +02:00
VERSION Version up to 6.2.0.pre 2013-09-25 14:04:32 +03:00

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 production installation

Official development installation

If you want to contribute, please first read our Contributing Guidelines and then we suggest you to use the Vagrant virtual machine project to get an environment working with all dependencies.

Unofficial production installations

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
bundle exec rake sidekiq: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

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

  • Unofficial #gitlab IRC on Freenode is another way to get in touch with other GitLab users who may be able to help you.

  • 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 allows you hire GitLab experts for installations, upgrades and customizations.

Getting in touch