Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 12-9-stable
  • 12-7-stable
  • 12-6-stable
  • 12-8-stable
  • github/fork/Kloppi313/patch-1
  • 12-5-stable
  • 12-4-stable
  • github/fork/ramalokesh8477/master
  • 12-1-stable
  • 12-2-stable
  • 12-0-stable
  • 12-3-stable
  • 42-42-stable
  • github/fork/hussamgit398/patch-2
  • 12-3-auto-deploy-20190911
  • 12-3-auto-deploy-20190916
  • 12-3-auto-deploy-20190908
  • 12-3-auto-deploy-20190901
  • 12-3-auto-deploy-20190901-32664
  • v12.10.0.pre
  • v12.9.0
  • v12.9.0-rc42
  • v12.8.7
  • v12.8.6
  • v12.8.5
  • v12.8.4
  • v12.8.3
  • v12.6.8
  • v12.7.7
  • v12.8.2
  • v12.8.1
  • v12.9.0.pre
  • v12.8.0
  • v12.8.0-rc42
  • v12.5.10
  • v12.7.6
  • v12.6.7
  • v12.7.5
  • v12.5.9
40 results

backup_rake_spec.rb

  • Kamil Trzcińśki's avatar
    120f9aba
    Add GitLab Pages · 120f9aba
    Kamil Trzcińśki 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
    120f9aba
    History
    Add GitLab Pages
    Kamil Trzcińśki 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