1. 22 Feb, 2016 1 commit
  2. 18 Dec, 2015 5 commits
    • Kamil Trzciński's avatar
    • Kamil Trzciński's avatar
      Bring back GitLab Pages SSL config · 2f51a361
      Kamil Trzciński authored
      2f51a361
    • Kamil Trzciński's avatar
      Revert "Store pages in shared/pages/fqdn/fqdn/public or... · f875e710
      Kamil Trzciński authored
      Revert "Store pages in shared/pages/fqdn/fqdn/public or shared/pages/fqdn/subpath/public - makes it simpler to implement CNAMEs in future"
      
      This reverts commit 86a2a78f0d13a678899460638add6b862059433e.
      f875e710
    • Kamil Trzciński's avatar
      Store pages in shared/pages/fqdn/fqdn/public or... · 355ca2ed
      Kamil Trzciński authored
      Store pages in shared/pages/fqdn/fqdn/public or shared/pages/fqdn/subpath/public - makes it simpler to implement CNAMEs in future
      355ca2ed
    • Kamil Trzciński's avatar
      Add GitLab Pages · 650d6a63
      Kamil Trzciński authored
      - The pages are created when build artifacts for `pages` job are uploaded
      - Pages serve the content under: http://group.pages.domain.com/project
      - Pages can be used to serve the group page, special project named as host: group.pages.domain.com
      - User can provide own 403 and 404 error pages by creating 403.html and 404.html in group page project
      - Pages can be explicitly removed from the project by clicking Remove Pages in Project Settings
      - The size of pages is limited by Application Setting: max pages size, which limits the maximum size of unpacked archive (default: 100MB)
      - The public/ is extracted from artifacts and content is served as static pages
      - Pages asynchronous worker use `dd` to limit the unpacked tar size
      - Pages needs to be explicitly enabled and domain needs to be specified in gitlab.yml
      - Pages are part of backups
      - Pages notify the deployment status using Commit Status API
      - Pages use a new sidekiq queue: pages
      - Pages use a separate nginx config which needs to be explicitly added
      650d6a63
  3. 11 Dec, 2015 1 commit
  4. 06 Dec, 2015 1 commit
  5. 27 Nov, 2015 3 commits
  6. 19 Nov, 2015 4 commits
  7. 18 Nov, 2015 1 commit
  8. 16 Nov, 2015 1 commit
  9. 10 Nov, 2015 2 commits
  10. 29 Oct, 2015 1 commit
  11. 14 Oct, 2015 1 commit
  12. 08 Oct, 2015 1 commit
  13. 22 Sep, 2015 1 commit
  14. 16 Sep, 2015 2 commits
  15. 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
  16. 31 Aug, 2015 1 commit
  17. 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
  18. 15 Jun, 2015 1 commit
  19. 11 Jun, 2015 1 commit
  20. 03 Mar, 2015 1 commit
  21. 20 Feb, 2015 3 commits
  22. 01 Jan, 2015 2 commits
  23. 03 Dec, 2014 2 commits
  24. 25 Nov, 2014 1 commit