Commit graph

6 commits

Author SHA1 Message Date
Achilleas Pipinellis
50bbc326a4 Change NGINX pages configs to account for the Pages daemon 2017-01-31 22:55:28 +00:00
Kamil Trzcinski
c66b15803a Fix confusing implementation detail in nginx config about how gitlab-pages work [ci skip] 2017-01-31 22:53:56 +00:00
Kamil Trzcinski
6c9ba469d9 Bring back GitLab Pages SSL config 2017-01-31 22:53:56 +00:00
Kamil Trzcinski
4afab3d4b6 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.
2017-01-31 22:53:55 +00:00
Kamil Trzcinski
94fdf58a87 Store pages in shared/pages/fqdn/fqdn/public or shared/pages/fqdn/subpath/public - makes it simpler to implement CNAMEs in future 2017-01-31 22:53:55 +00:00
Kamil Trzcinski
120f9abaa1 Add GitLab Pages
- 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
2017-01-31 22:50:39 +00:00