- 06 Apr, 2017 1 commit
-
-
Jacob Vosmaer authored
-
- 21 Mar, 2017 1 commit
-
-
Jacob Vosmaer authored
-
- 08 Mar, 2017 1 commit
-
-
Nick Thomas authored
-
- 03 Mar, 2017 2 commits
-
-
3kami3 authored
Fixed issues pointed out.
-
Paweł Chojnacki authored
-
- 01 Mar, 2017 1 commit
-
- 07 Feb, 2017 1 commit
-
-
Drew Blessing authored
Cherry-picked ‘Fix syntax error in conditional statement’
-
- 31 Jan, 2017 13 commits
-
-
Achilleas Pipinellis authored
-
Achilleas Pipinellis authored
-
Achilleas Pipinellis authored
No need to be executable since it is sourced in /etc/init.d/gitlab
-
Achilleas Pipinellis authored
-
Achilleas Pipinellis authored
[ci skip]
-
Achilleas Pipinellis authored
So as to be consistent with what is set in Omnibus
-
Achilleas Pipinellis authored
-
Achilleas Pipinellis authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski 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 Trzcinski authored
Store pages in shared/pages/fqdn/fqdn/public or shared/pages/fqdn/subpath/public - makes it simpler to implement CNAMEs in future
-
Kamil Trzcinski 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
-
- 27 Jan, 2017 1 commit
-
-
Mike Greiling authored
-
- 12 Dec, 2016 1 commit
-
-
Nick Thomas authored
-
- 08 Aug, 2016 1 commit
-
-
Jacob Vosmaer authored
This reverts commit 47b5b441. See https://gitlab.com/gitlab-org/gitlab-ce/issues/17877#note_13488047
-
- 12 Jul, 2016 1 commit
-
-
Jacob Vosmaer authored
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/17877 . This change adds 'defense in depth' against 'Host' HTTP header injection. It affects normal users in the following way. Suppose your GitLab server has IP address 1.2.3.4 and hostname gitlab.example.com. Currently, if you enter 1.2.3.4 in your browser, you get redirected to 1.2.3.4/users/sign_in. After this change, you get redirected from 1.2.3.4 to gitlab.example.com/users/sign_in. This is because the address you typed in the address bar of your browser ('1.2.3.4'), which gets stored in the 'Host' header, is now being overwritten to 'gitlab.example.com' in NGINX. In this change we also make NGINX clear the 'X-Forwarded-Host' header because Ruby on Rails also uses that header the same wayas the 'Host' header. We think that for most GitLab servers this is the right behavior, and if not then administrators can change this behavior themselves at the NGINX level.
-
- 03 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 3e991230.
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- 23 May, 2016 1 commit
-
-
Achilleas Pipinellis authored
-
- 22 May, 2016 1 commit
-
-
Achilleas Pipinellis authored
-
- 28 Apr, 2016 1 commit
-
-
Achilleas Pipinellis authored
-
- 22 Apr, 2016 1 commit
-
-
Robert Speicher authored
[ci skip] Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/15398
-
- 14 Apr, 2016 1 commit
-
-
Achilleas Pipinellis authored
-
- 11 Mar, 2016 1 commit
-
-
Artem Sidorenko authored
Otherwise this might 'hide' problems https://github.com/gitlabhq/gitlabhq/issues/10053#issuecomment-188919319
-
- 09 Feb, 2016 1 commit
-
-
Achilleas Pipinellis authored
[ci skip]
-
- 08 Feb, 2016 2 commits
-
-
ritave authored
-s flag of su doesn't work correctly on some systems, loging in the user and not running the requested command. By moving the bash shell init inside the su command we avoid the issue
-
Harald Spaethe authored
-
- 25 Jan, 2016 1 commit
-
-
fbretel authored
-
- 21 Jan, 2016 1 commit
-
-
Jacob Vosmaer authored
-
- 24 Dec, 2015 1 commit
-
-
cafuego authored
-
- 15 Dec, 2015 1 commit
-
-
Jacob Vosmaer authored
-
- 11 Dec, 2015 1 commit
-
-
Jacob Vosmaer authored
-