- 22 Feb, 2016 1 commit
-
-
Achilleas Pipinellis authored
Pages docs See merge request !202
-
- 18 Dec, 2015 5 commits
-
-
Kamil Trzciński authored
-
Kamil Trzciński authored
-
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.
-
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
-
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
-
- 11 Dec, 2015 1 commit
-
-
Jacob Vosmaer authored
-
- 06 Dec, 2015 1 commit
-
-
Vyacheslav Stetskevych authored
-
- 27 Nov, 2015 3 commits
-
-
Robert Speicher authored
[ci skip]
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
It turns out that if we do not the declaration from "location /" wins.
-
- 19 Nov, 2015 4 commits
-
-
Robert Speicher authored
Conflicts remaining: - app/controllers/groups/group_members_controller.rb - app/controllers/projects/project_members_controller.rb - app/models/ability.rb - app/models/member.rb - app/models/project.rb
-
Dmitriy Zaporozhets authored
Deploy page should be shown for all pages not just root Related to change already merged to Omnibus - omnibus-gitlab!540 This change makes it so the deploy page is shown on all GitLab pages if the page exists. Users will no longer receive the 502 when deploys are happening. See merge request !1828
-
Robert Speicher authored
Do not limit workhorse POST/PUT size in NGINX Limiting, if any, should happen in gitlab-workhorse. See merge request !1831
-
Jacob Vosmaer authored
Limiting, if any, should happen in gitlab-workhorse.
-
- 18 Nov, 2015 1 commit
-
-
Drew Blessing authored
-
- 16 Nov, 2015 1 commit
-
-
Marin Jankovski authored
-
- 10 Nov, 2015 2 commits
-
-
Kamil Trzciński authored
-
Kamil Trzciński authored
- Offloads uploading to GitLab Workhorse - Use /authorize request for fast uploading - Added backup recipes for artifacts - Support download acceleration using X-Sendfile
-
- 29 Oct, 2015 1 commit
-
-
Jacob Vosmaer authored
-
- 14 Oct, 2015 1 commit
-
-
Jacob Vosmaer authored
Users are allowed to supply namespace%2Fproject instead of a numeric ID
-
- 08 Oct, 2015 1 commit
-
-
Jacob Vosmaer authored
This change relies on changes in gitlab_git and gitlab-git-http-server.
-
- 22 Sep, 2015 1 commit
-
-
Kamil Trzciński authored
-
- 16 Sep, 2015 2 commits
-
-
Kamil Trzciński authored
-
Kamil Trzciński authored
-
- 07 Sep, 2015 2 commits
-
-
Jacob Vosmaer authored
-
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).
-
- 31 Aug, 2015 1 commit
-
-
Jacob Vosmaer authored
-
- 28 Jul, 2015 1 commit
-
-
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 Jun, 2015 1 commit
-
-
Marin Jankovski authored
-
- 11 Jun, 2015 1 commit
-
-
Marin Jankovski authored
-
- 03 Mar, 2015 1 commit
-
-
Douwe Maan authored
Revert "Merge branch 'go-get-workaround-nginx' of https://github.com/mattes/gitlabhq into mattes-go-get-workaround-nginx" This reverts commit 51349ca3, reversing changes made to b180476b.
-
- 20 Feb, 2015 3 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 01 Jan, 2015 2 commits
-
-
Matthias Kadenbach authored
-
Matthias Kadenbach authored
-
- 03 Dec, 2014 2 commits
-
-
Luke Ashe-Browne authored
-
Luke Ashe-Browne authored
We want to make users aware that the nginx default config will conflict with the gitlab default_server conf file.
-
- 25 Nov, 2014 1 commit
-
-
sbeh authored
This will ensure nginx starts up without the following errors messages: nginx: [emerg] bind() to [::]:443 failed (98: Address already in use) nginx: [emerg] bind() to [::]:443 failed (98: Address already in use) nginx: [emerg] bind() to [::]:443 failed (98: Address already in use) nginx: [emerg] bind() to [::]:443 failed (98: Address already in use) nginx: [emerg] bind() to [::]:443 failed (98: Address already in use) nginx: [emerg] still could not bind() Googling for them leads you to this site: https://chrisjean.com/2014/02/10/fix-nginx-emerg-bind-to-80-failed-98-address-already-in-use/
-