BigW Consortium Gitlab

  1. 04 Feb, 2016 1 commit
  2. 02 Feb, 2016 1 commit
  3. 15 Dec, 2015 1 commit
  4. 11 Dec, 2015 3 commits
  5. 18 Nov, 2015 1 commit
  6. 16 Nov, 2015 1 commit
  7. 29 Oct, 2015 1 commit
  8. 22 Oct, 2015 1 commit
    • Fix cloning Wiki repositories via HTTP · 64a270a6
      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
  9. 21 Oct, 2015 1 commit
  10. 09 Oct, 2015 1 commit
  11. 08 Oct, 2015 1 commit
  12. 02 Sep, 2015 2 commits
  13. 31 Aug, 2015 1 commit
  14. 11 Aug, 2015 2 commits
  15. 28 Jul, 2015 4 commits
  16. 15 Jul, 2015 1 commit
  17. 23 Jun, 2015 1 commit
  18. 03 Jun, 2015 1 commit
    • Move repository when project is removed · 97ff86e0
      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: 's avatarDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
  19. 22 May, 2015 1 commit
  20. 06 Apr, 2015 1 commit
  21. 24 Mar, 2015 2 commits
  22. 02 Mar, 2015 1 commit
  23. 23 Feb, 2015 1 commit
  24. 03 Feb, 2015 2 commits
  25. 28 Jan, 2015 1 commit
  26. 06 Jan, 2015 1 commit
    • White-list requests from 127.0.0.1 · af56c1dd
      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.
  27. 18 Dec, 2014 1 commit
  28. 15 Dec, 2014 1 commit
  29. 18 Nov, 2014 3 commits