- 18 Nov, 2015 1 commit
-
-
Douwe Maan authored
-
- 16 Nov, 2015 1 commit
-
-
Marin Jankovski authored
-
- 29 Oct, 2015 1 commit
-
-
Jacob Vosmaer authored
-
- 22 Oct, 2015 1 commit
-
-
Stan Hu authored
Cloning a project Wiki over HTTP would end up cloning the main repository since the .wiki extension was being stripped. Closes #3106
-
- 09 Oct, 2015 1 commit
-
-
Robert Speicher authored
gitlab-shell expects only one tab separator per key, and an SSH key with a tab character in the comment, for example, would break things. Closes #2970
-
- 08 Oct, 2015 1 commit
-
-
Jacob Vosmaer authored
This change relies on changes in gitlab_git and gitlab-git-http-server.
-
- 02 Sep, 2015 2 commits
-
-
Jacob Vosmaer authored
This is the quickest/dumbest/safest way I could think of to prevent the instance variable reuse problems we have on dev.gitlab.org now.
-
Kirilll Zaitsev authored
-
- 31 Aug, 2015 1 commit
-
-
Jacob Vosmaer authored
-
- 11 Aug, 2015 2 commits
-
-
Dmitriy Zaporozhets authored
This reverts commit 5daf44b7, reversing changes made to 2f706fbd.
-
Dmitriy Zaporozhets authored
This reverts commit 957e849f, reversing changes made to 6b9dbe9f. Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 28 Jul, 2015 4 commits
-
-
GitLab authored
To make Rubocop and Douwe happy
-
GitLab authored
-
GitLab authored
-
Jacob Vosmaer authored
https://gitlab.com/gitlab-org/gitlab-git-http-server This change introduces the GITLAB_GRACK_AUTH_ONLY environment variable. When set, Grack requests to GitLab will only respond with the user's GL_ID (if the request is OK) or an error. This allows gitlab-git-http-server to use the main GitLab application as an authentication and authorization backend. If we like how this works we should drop the GITLAB_GRACK_AUTH_ONLY variable at some point in the future.
-
- 15 Jul, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 23 Jun, 2015 1 commit
-
-
Stan Hu authored
Closes #1225 Closes #1854 Closes #1858
-
- 03 Jun, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
Ths commit does next: * When we remove project we move repository to path+deleted.git * Then we schedule removal of path+deleted with sidekiq * If repository move failed we abort project removal This should help us with NFS issue when project get removed but repository stayed. The full explanation of problem is below: * rm -rf project.git * rm -rf removes project.git/objects/foo * NFS server renames foo to foo.nfsXXXX because some NFS client (think * Unicorn) still has the file open * rm -rf exits, but project.git/objects/foo.nfsXXX still exists * Unicorn closes the file, the NFS client closes the file (foo), and the * NFS server removes foo.nfsXXX * the directory project.git/objects/ still exists => problem So now we move repository and even if repository removal failed Repository directory is moved so no bugs with project removed but repository directory taken. User still able to create new project with same name. From administrator perspective you can easily find stalled repositories by searching `*+deleted.git` Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 22 May, 2015 1 commit
-
-
Stan Hu authored
-
- 06 Apr, 2015 1 commit
-
-
Douwe Maan authored
-
- 24 Mar, 2015 2 commits
-
-
Douwe Maan authored
-
Stan Hu authored
successful Git over HTTP authentication. Add logging when a ban goes into effect for debugging. Issue #1171
-
- 02 Mar, 2015 1 commit
-
-
Douwe Maan authored
-
- 23 Feb, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 03 Feb, 2015 2 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 28 Jan, 2015 1 commit
-
-
Valery Sizov authored
-
- 06 Jan, 2015 1 commit
-
-
Jacob Vosmaer authored
On some misconfigured GitLab servers, if you look in production.log it looks like all requests come from 127.0.0.1. To avoid unwanted banning we white-list 127.0.0.1 with this commit.
-
- 18 Dec, 2014 1 commit
-
-
Jacob Vosmaer authored
-
- 15 Dec, 2014 1 commit
-
-
Jacob Vosmaer authored
-
- 18 Nov, 2014 3 commits
-
-
Dmitriy Zaporozhets authored
This reverts commit 533f4cdf.
-
Valery Sizov authored
Conflicts: lib/gitlab/git_access.rb spec/lib/gitlab/git_access_spec.rb
-
Ciro Santilli authored
Before this it would fail because git hooks automatically prepend things to the path, which can lead the wrong Ruby version to be called in which dependencies are not installed. To make sure that this is correct, the forked_merge_requests commented out test that depends on this change was uncommented. For that test to pass, it is also necessary to setup the mock server on port 3001 under test_env.rb.
-
- 06 Nov, 2014 2 commits
-
-
Valery Sizov authored
This reverts commit b33d4bc2.
-
Valery Sizov authored
This reverts commit 0b1084a4.
-
- 05 Nov, 2014 2 commits
-
-
Ciro Santilli authored
-
Ciro Santilli authored
It pollutes the test output too much.
-
- 31 Oct, 2014 1 commit
-
-
Ciro Santilli authored
-
- 21 Oct, 2014 1 commit
-
-
Ciro Santilli authored
-
- 03 Oct, 2014 1 commit
-
-
Ciro Santilli authored
-