120f9abaa1
- 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 |
||
|---|---|---|
| .. | ||
| backup_rake_spec.rb | ||
| check_rake_spec.rb | ||
| db_rake_spec.rb | ||
| ldap_rake_spec.rb | ||
| mail_google_schema_whitelisting.rb | ||
| shell_rake_spec.rb | ||
| task_helpers_spec.rb | ||
| users_rake_spec.rb | ||
| workhorse_rake_spec.rb | ||