An error occurred fetching the project authors.
  1. 11 Dec, 2015 1 commit
  2. 06 Dec, 2015 1 commit
  3. 27 Nov, 2015 2 commits
  4. 19 Nov, 2015 1 commit
  5. 18 Nov, 2015 1 commit
  6. 16 Nov, 2015 1 commit
  7. 10 Nov, 2015 2 commits
  8. 29 Oct, 2015 1 commit
  9. 14 Oct, 2015 1 commit
  10. 08 Oct, 2015 1 commit
  11. 07 Sep, 2015 2 commits
    • Jacob Vosmaer's avatar
      The good stuff needs NGINX 1.7.11 · 783791fd
      Jacob Vosmaer authored
      783791fd
    • Jacob Vosmaer's avatar
      Do not let NGINX buffer Git HTTP requests · 8d59b1ac
      Jacob Vosmaer authored
      Before this change NGINX would convert a chunked HTTP POST (e.g.
      git push) into a HTTP 1.0 single large POST. This creates an
      unnecessary delay, and it creates unnecessary memory pressure on
      gitlab-git-http-server.
      
      For the response ('proxy_buffering') I am less sure that NGINX 's
      buffering behavior is harmful, but it still makes more sense to me
      not to interfere with gitlab-git-http-server (and the Golang net/http
      server).
      8d59b1ac
  12. 31 Aug, 2015 1 commit
  13. 28 Jul, 2015 1 commit
    • Jacob Vosmaer's avatar
      Experimental support for gitlab-git-http-server · d3305df7
      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.
      d3305df7
  14. 15 Jun, 2015 1 commit
  15. 11 Jun, 2015 1 commit
  16. 03 Mar, 2015 1 commit
  17. 20 Feb, 2015 3 commits
  18. 01 Jan, 2015 2 commits
  19. 03 Dec, 2014 1 commit
  20. 25 Nov, 2014 1 commit
  21. 09 Nov, 2014 1 commit
  22. 03 Nov, 2014 1 commit
    • Hugo Osvaldo Barrera's avatar
      Don't enable IPv4 *only* on nginx. · e3098b69
      Hugo Osvaldo Barrera authored
      The current configuration sample files only enable IPv4 by default, making the
      server inaccesible for many remote hosts (and an increasing amount every day).
      
      Enable IPv4 and IPv6 by default. Older servers with no external IPv6
      connectivity will not fail since they'll have a local-link IPv6 address to bind
      to anyway.
      e3098b69
  23. 16 Oct, 2014 2 commits
  24. 10 Oct, 2014 2 commits
  25. 12 Sep, 2014 1 commit
  26. 08 Sep, 2014 1 commit
  27. 07 Sep, 2014 2 commits
  28. 01 Sep, 2014 1 commit
  29. 23 Aug, 2014 3 commits