# Exploring GitLab Pages
> 原文：[https://docs.gitlab.com/ee/user/project/pages/introduction.html](https://docs.gitlab.com/ee/user/project/pages/introduction.html)
* [GitLab Pages requirements](#gitlab-pages-requirements)
* [GitLab Pages on GitLab.com](#gitlab-pages-on-gitlabcom)
* [Example projects](#example-projects)
* [Custom error codes Pages](#custom-error-codes-pages)
* [Redirects in GitLab Pages](#redirects-in-gitlab-pages)
* [GitLab Pages Access Control](#gitlab-pages-access-control-core)
* [Unpublishing your Pages](#unpublishing-your-pages)
* [Limitations](#limitations)
* [Specific configuration options for Pages](#specific-configuration-options-for-pages)
* [`.gitlab-ci.yml` for plain HTML websites](#gitlab-ciyml-for-plain-html-websites)
* [`.gitlab-ci.yml` for a static site generator](#gitlab-ciyml-for-a-static-site-generator)
* [`.gitlab-ci.yml` for a repository where there’s also actual code](#gitlab-ciyml-for-a-repository-where-theres-also-actual-code)
* [Serving compressed assets](#serving-compressed-assets)
* [Resolving ambiguous URLs](#resolving-ambiguous-urls)
* [Frequently Asked Questions](#frequently-asked-questions)
* [Can I download my generated pages?](#can-i-download-my-generated-pages)
* [Can I use GitLab Pages if my project is private?](#can-i-use-gitlab-pages-if-my-project-is-private)
* [Do I need to create a user/group website before creating a project website?](#do-i-need-to-create-a-usergroup-website-before-creating-a-project-website)
* [Known issues](#known-issues)
# Exploring GitLab Pages[](#exploring-gitlab-pages "Permalink")
本文檔是用戶指南，用于探索 GitLab Pages 提供的選項和設置.
首先要熟悉 GitLab 頁面：
* 閱讀[有關 GitLab Pages](index.html#overview)的[介紹](index.html#overview) .
* Learn [how to get started with Pages](index.html#getting-started).
* 在[管理員文檔中](../../../administration/pages/index.html)了解如何在整個 GitLab 實例上啟用 GitLab 頁面.
## GitLab Pages requirements[](#gitlab-pages-requirements "Permalink")
簡而言之，這是您需要在 GitLab 頁面中上傳網站的內容：
1. 實例的域：用于 GitLab 頁面的域名（詢問管理員）.
2. GitLab CI / CD：一個`.gitlab-ci.yml`文件，在存儲庫的根目錄中有一個名為[`pages`](../../../ci/yaml/README.html#pages)的特定作業.
3. 您網站存儲庫中一個名為`public`的目錄，其中包含要發布的內容.
4. 為項目啟用了 GitLab Runner.
## GitLab Pages on GitLab.com[](#gitlab-pages-on-gitlabcom "Permalink")
如果您使用[GitLab.com](#gitlab-pages-on-gitlabcom)上的[GitLab 頁面](#gitlab-pages-on-gitlabcom)來托管您的網站，則：
* The domain name for GitLab Pages on GitLab.com is `gitlab.io`.
* 自定義域和 TLS 支持已啟用.
* 共享運行器默認情況下處于啟用狀態，免費提供，可用于構建您的網站. 如果您愿意，仍然可以攜帶自己的跑步者.
## Example projects[](#example-projects "Permalink")
訪問[GitLab 頁面組](https://gitlab.com/groups/pages)以獲得示例項目的完整列表. 歡迎捐款.
## Custom error codes Pages[](#custom-error-codes-pages "Permalink")
您可以通過在將包含在工件中的`public/`目錄的根目錄中分別創建`403.html`和`404.html`文件來提供自己的 403 和 404 錯誤頁面. 通常，這是項目的根目錄，但是根據您的靜態生成器配置，它可能有所不同.
如果是`404.html` ，則有不同的方案. 例如：
* 如果您使用項目 Pages（在`/projectname/` ）并嘗試訪問`/projectname/non/existing_file` ，則 GitLab Pages 將嘗試首先提供`/projectname/404.html` ，然后提供`/404.html` .
* 如果您使用用戶/組頁面（在`/`下提供）并嘗試訪問`/non/existing_file` GitLab Pages 將嘗試提供`/404.html` .
* 如果您使用自定義域并嘗試訪問`/non/existing_file` ，則 GitLab Pages 將嘗試僅提供`/404.html` .
## Redirects in GitLab Pages[](#redirects-in-gitlab-pages "Permalink")
由于您不能使用任何自定義服務器配置文件（例如`.htaccess`或任何`.conf`文件），因此，如果要將頁面重定向到其他位置，可以使用[HTTP meta refresh 標簽](https://en.wikipedia.org/wiki/Meta_refresh) .
一些靜態網站生成器提供了該功能的插件，因此您不必手動創建和編輯 HTML 文件. 例如，Jekyll 具有[redirect-from 插件](https://github.com/jekyll/jekyll-redirect-from) .
## GitLab Pages Access Control[](#gitlab-pages-access-control-core "Permalink")
要限制對您網站的訪問，請啟用[GitLab 頁面訪問控制](pages_access_control.html) .
## Unpublishing your Pages[](#unpublishing-your-pages "Permalink")
如果您需要清除 Pages 內容，可以通過右上角的齒輪圖標進入項目設置，然后導航至**Pages** . 點擊**刪除頁面**按鈕，您的頁面網站將被刪除.
[](img/remove_pages.png)
## Limitations[](#limitations "Permalink")
在 GitLab 實例的常規域（ `*.example.io` ）下使用 Pages 時， *不能*將 HTTPS 與子子域一起使用. 這意味著，如果你的用戶名或組名稱中包含一個圓點，例如`foo.bar` ，域`https://foo.bar.example.io`將*無法*正常工作. 這是[HTTP Over TLS 協議](https://tools.ietf.org/html/rfc2818#section-3.1)的限制. 如果您不將 HTTP 重定向到 HTTPS，HTTP 頁面將繼續工作.
GitLab 網頁[**不**支持組為網站分組](../../group/subgroups/index.html#limitations) . 您只能創建最高級別的群組網站.
## Specific configuration options for Pages[](#specific-configuration-options-for-pages "Permalink")
了解如何針對特定用例設置 GitLab CI / CD.
### `.gitlab-ci.yml` for plain HTML websites[](#gitlab-ciyml-for-plain-html-websites "Permalink")
假設您的存儲庫包含以下文件：
```
├── index.html
├── css
│ └── main.css
└── js
└── main.js
```
然后，下面的`.gitlab-ci.yml`示例僅將所有文件從項目的根目錄移至`public/`目錄. `.public`解決方法是， `cp`不會在無限循環中將`public/`復制到自身：
```
pages:
script:
- mkdir .public
- cp -r * .public
- mv .public public
artifacts:
paths:
- public
only:
- master
```
### `.gitlab-ci.yml` for a static site generator[](#gitlab-ciyml-for-a-static-site-generator "Permalink")
請參閱本文檔，以獲取[分步指南](getting_started/pages_from_scratch.html) .
### `.gitlab-ci.yml` for a repository where there’s also actual code[](#gitlab-ciyml-for-a-repository-where-theres-also-actual-code "Permalink")
請記住，默認情況下，GitLab 頁面是分支/標簽不可知的，它們的部署僅取決于您在`.gitlab-ci.yml`指定`.gitlab-ci.yml` . 每當將新的提交推送到專門用于頁面的分支時，就可以使用[`only`參數](../../../ci/yaml/README.html#onlyexcept-basic)限制`pages`作業.
這樣，您可以將項目的代碼保存在`master`分支中，并使用一個孤兒分支（將其命名為`pages` ）來托管您的靜態生成器站點.
您可以這樣創建一個新的空分支：
```
git checkout --orphan pages
```
在這個新分支上進行的第一次提交將沒有父母，這將是與所有其他分支和提交完全脫節的新歷史的根源. 在`pages`分支中推送靜態生成器的源文件.
以下是`.gitlab-ci.yml`的副本，其中最重要的一行是最后一行，指定要執行`pages`分支中的所有`pages` ：
```
image: ruby:2.6
pages:
script:
- gem install jekyll
- jekyll build -d public/
artifacts:
paths:
- public
only:
- pages
```
請參見一個示例，該示例在[`master`分支](https://gitlab.com/pages/jekyll-branched/tree/master)中具有不同的文件，而 Jekyll 的源文件在[`pages`分支中](https://gitlab.com/pages/jekyll-branched/tree/pages) ，該[分支](https://gitlab.com/pages/jekyll-branched/tree/pages)還包含`.gitlab-ci.yml` .
### Serving compressed assets[](#serving-compressed-assets "Permalink")
大多數現代的瀏覽器都支持下載壓縮格式的文件. 通過減小文件大小，可以加快下載速度.
Pages 將提供未壓縮的文件之前，將檢查是否存在擴展名為`.gz`的相同文件. 如果支持，并且瀏覽器支持接收壓縮文件，它將使用該版本而不是未壓縮版本.
要利用此功能，您上傳到頁面的工件應具有以下結構：
```
public/
├─┬ index.html
│ └ index.html.gz
│
├── css/
│ └─┬ main.css
│ └ main.css.gz
│
└── js/
└─┬ main.js
└ main.js.gz
```
這可以通過在`.gitlab-ci.yml`頁面作業中包含以下`script:`來實現：
```
pages:
# Other directives
script:
# Build the public/ directory first
- find public -type f -regex '.*\.\(htm\|html\|txt\|text\|js\|css\)$' -exec gzip -f -k {} \;
```
通過預壓縮文件并在工件中包括兩個版本，Pages 可以處理對壓縮和未壓縮內容的請求，而無需按需壓縮文件.
### Resolving ambiguous URLs[](#resolving-ambiguous-urls "Permalink")
在 GitLab 11.8 中[引入](https://gitlab.com/gitlab-org/gitlab-pages/-/issues/95)
當接收到不包含擴展名的 URL 的請求時，GitLab Pages 會假設要提供哪些文件.
考慮使用以下文件部署的 Pages 站點：
```
public/
├─┬ index.html
│ ├ data.html
│ └ info.html
│
├── data/
│ └── index.html
├── info/
│ └── details.html
└── other/
└── index.html
```
頁面支持通過幾個不同的 URL 來訪問每個文件. 特別是，如果 URL 僅指定目錄，它將始終尋找`index.html`文件. 如果該 URL 引用了一個不存在的文件，但是將`.html`添加到該 URL 中會導致該文件*確實*存在，將改為提供該文件. 以下是在上述 Pages 網站上發生的情況的一些示例：
| URL path | HTTP 響應 | 文件送達 |
| --- | --- | --- |
| `/` | `200 OK` | `public/index.html` |
| `/index.html` | `200 OK` | `public/index.html` |
| `/index` | `200 OK` | `public/index.html` |
| `/data` | `200 OK` | `public/data/index.html` |
| `/data/` | `200 OK` | `public/data/index.html` |
| `/data.html` | `200 OK` | `public/data.html` |
| `/info` | `200 OK` | `public/info.html` |
| `/info/` | `200 OK` | `public/info.html` |
| `/info.html` | `200 OK` | `public/info.html` |
| `/info/details` | `200 OK` | `public/info/details.html` |
| `/info/details.html` | `200 OK` | `public/info/details.html` |
| `/other` | `302 Found` | `public/other/index.html` |
| `/other/` | `200 OK` | `public/other/index.html` |
| `/other/index` | `200 OK` | `public/other/index.html` |
| `/other/index.html` | `200 OK` | `public/other/index.html` |
**注意：**當存在`public/data/index.html`時，對于`/data`和`/data/` URL 路徑，其優先于`public/data.html`文件.
## Frequently Asked Questions[](#frequently-asked-questions "Permalink")
### Can I download my generated pages?[](#can-i-download-my-generated-pages "Permalink")
當然. 您需要做的就是從作業頁面下載工件存檔.
### Can I use GitLab Pages if my project is private?[](#can-i-use-gitlab-pages-if-my-project-is-private "Permalink")
是. GitLab Pages 不在乎將項目的可見性級別設置為私有，內部還是公共.
### Do I need to create a user/group website before creating a project website?[](#do-i-need-to-create-a-usergroup-website-before-creating-a-project-website "Permalink")
不，你沒有. 您可以先創建您的項目，然后將在`http(s)://namespace.example.io/projectname`下對其進行訪問.
## Known issues[](#known-issues "Permalink")
有關已知問題的列表，請訪問 GitLab 的[公共問題跟蹤器](https://gitlab.com/gitlab-org/gitlab/-/issues?label_name[]=Category:Pages) .
- GitLab Docs
- Installation
- Requirements
- GitLab cloud native Helm Chart
- Install GitLab with Docker
- Installation from source
- Install GitLab on Microsoft Azure
- Installing GitLab on Google Cloud Platform
- Installing GitLab on Amazon Web Services (AWS)
- Analytics
- Code Review Analytics
- Productivity Analytics
- Value Stream Analytics
- Kubernetes clusters
- Adding and removing Kubernetes clusters
- Adding EKS clusters
- Adding GKE clusters
- Group-level Kubernetes clusters
- Instance-level Kubernetes clusters
- Canary Deployments
- Cluster Environments
- Deploy Boards
- GitLab Managed Apps
- Crossplane configuration
- Cluster management project (alpha)
- Kubernetes Logs
- Runbooks
- Serverless
- Deploying AWS Lambda function using GitLab CI/CD
- Securing your deployed applications
- Groups
- Contribution Analytics
- Custom group-level project templates
- Epics
- Manage epics
- Group Import/Export
- Insights
- Issues Analytics
- Iterations
- Public access
- SAML SSO for GitLab.com groups
- SCIM provisioning using SAML SSO for GitLab.com groups
- Subgroups
- Roadmap
- Projects
- GitLab Secure
- Security Configuration
- Container Scanning
- Dependency Scanning
- Dependency List
- Static Application Security Testing (SAST)
- Secret Detection
- Dynamic Application Security Testing (DAST)
- GitLab Security Dashboard
- Offline environments
- Standalone Vulnerability pages
- Security scanner integration
- Badges
- Bulk editing issues and merge requests at the project level
- Code Owners
- Compliance
- License Compliance
- Compliance Dashboard
- Create a project
- Description templates
- Deploy Keys
- Deploy Tokens
- File finder
- Project integrations
- Integrations
- Atlassian Bamboo CI Service
- Bugzilla Service
- Custom Issue Tracker service
- Discord Notifications service
- Enabling emails on push
- GitHub project integration
- Hangouts Chat service
- Atlassian HipChat
- Irker IRC Gateway
- GitLab Jira integration
- Mattermost Notifications Service
- Mattermost slash commands
- Microsoft Teams service
- Mock CI Service
- Prometheus integration
- Redmine Service
- Slack Notifications Service
- Slack slash commands
- GitLab Slack application
- Webhooks
- YouTrack Service
- Insights
- Issues
- Crosslinking Issues
- Design Management
- Confidential issues
- Due dates
- Issue Boards
- Issue Data and Actions
- Labels
- Managing issues
- Milestones
- Multiple Assignees for Issues
- Related issues
- Service Desk
- Sorting and ordering issue lists
- Issue weight
- Associate a Zoom meeting with an issue
- Merge requests
- Allow collaboration on merge requests across forks
- Merge Request Approvals
- Browser Performance Testing
- How to create a merge request
- Cherry-pick changes
- Code Quality
- Load Performance Testing
- Merge Request dependencies
- Fast-forward merge requests
- Merge when pipeline succeeds
- Merge request conflict resolution
- Reverting changes
- Reviewing and managing merge requests
- Squash and merge
- Merge requests versions
- Draft merge requests
- Members of a project
- Migrating projects to a GitLab instance
- Import your project from Bitbucket Cloud to GitLab
- Import your project from Bitbucket Server to GitLab
- Migrating from ClearCase
- Migrating from CVS
- Import your project from FogBugz to GitLab
- Gemnasium
- Import your project from GitHub to GitLab
- Project importing from GitLab.com to your private GitLab instance
- Import your project from Gitea to GitLab
- Import your Jira project issues to GitLab
- Migrating from Perforce Helix
- Import Phabricator tasks into a GitLab project
- Import multiple repositories by uploading a manifest file
- Import project from repo by URL
- Migrating from SVN to GitLab
- Migrating from TFVC to Git
- Push Options
- Releases
- Repository
- Branches
- Git Attributes
- File Locking
- Git file blame
- Git file history
- Repository mirroring
- Protected branches
- Protected tags
- Push Rules
- Reduce repository size
- Signing commits with GPG
- Syntax Highlighting
- GitLab Web Editor
- Web IDE
- Requirements Management
- Project settings
- Project import/export
- Project access tokens (Alpha)
- Share Projects with other Groups
- Snippets
- Static Site Editor
- Wiki
- Project operations
- Monitor metrics for your CI/CD environment
- Set up alerts for Prometheus metrics
- Embedding metric charts within GitLab-flavored Markdown
- Embedding Grafana charts
- Using the Metrics Dashboard
- Dashboard YAML properties
- Metrics dashboard settings
- Panel types for dashboards
- Using Variables
- Templating variables for metrics dashboards
- Prometheus Metrics library
- Monitoring AWS Resources
- Monitoring HAProxy
- Monitoring Kubernetes
- Monitoring NGINX
- Monitoring NGINX Ingress Controller
- Monitoring NGINX Ingress Controller with VTS metrics
- Alert Management
- Error Tracking
- Tracing
- Incident Management
- GitLab Status Page
- Feature Flags
- GitLab CI/CD
- GitLab CI/CD pipeline configuration reference
- GitLab CI/CD include examples
- Introduction to CI/CD with GitLab
- Getting started with GitLab CI/CD
- How to enable or disable GitLab CI/CD
- Using SSH keys with GitLab CI/CD
- Migrating from CircleCI
- Migrating from Jenkins
- Auto DevOps
- Getting started with Auto DevOps
- Requirements for Auto DevOps
- Customizing Auto DevOps
- Stages of Auto DevOps
- Upgrading PostgreSQL for Auto DevOps
- Cache dependencies in GitLab CI/CD
- GitLab ChatOps
- Cloud deployment
- Docker integration
- Building Docker images with GitLab CI/CD
- Using Docker images
- Building images with kaniko and GitLab CI/CD
- GitLab CI/CD environment variables
- Predefined environment variables reference
- Where variables can be used
- Deprecated GitLab CI/CD variables
- Environments and deployments
- Protected Environments
- GitLab CI/CD Examples
- Test a Clojure application with GitLab CI/CD
- Using Dpl as deployment tool
- Testing a Phoenix application with GitLab CI/CD
- End-to-end testing with GitLab CI/CD and WebdriverIO
- DevOps and Game Dev with GitLab CI/CD
- Deploy a Spring Boot application to Cloud Foundry with GitLab CI/CD
- How to deploy Maven projects to Artifactory with GitLab CI/CD
- Testing PHP projects
- Running Composer and NPM scripts with deployment via SCP in GitLab CI/CD
- Test and deploy Laravel applications with GitLab CI/CD and Envoy
- Test and deploy a Python application with GitLab CI/CD
- Test and deploy a Ruby application with GitLab CI/CD
- Test and deploy a Scala application to Heroku
- GitLab CI/CD for external repositories
- Using GitLab CI/CD with a Bitbucket Cloud repository
- Using GitLab CI/CD with a GitHub repository
- GitLab Pages
- GitLab Pages
- GitLab Pages domain names, URLs, and baseurls
- Create a GitLab Pages website from scratch
- Custom domains and SSL/TLS Certificates
- GitLab Pages integration with Let's Encrypt
- GitLab Pages Access Control
- Exploring GitLab Pages
- Incremental Rollouts with GitLab CI/CD
- Interactive Web Terminals
- Optimizing GitLab for large repositories
- Metrics Reports
- CI/CD pipelines
- Pipeline Architecture
- Directed Acyclic Graph
- Multi-project pipelines
- Parent-child pipelines
- Pipelines for Merge Requests
- Pipelines for Merged Results
- Merge Trains
- Job artifacts
- Pipeline schedules
- Pipeline settings
- Triggering pipelines through the API
- Review Apps
- Configuring GitLab Runners
- GitLab CI services examples
- Using MySQL
- Using PostgreSQL
- Using Redis
- Troubleshooting CI/CD
- GitLab Package Registry
- GitLab Container Registry
- Dependency Proxy
- GitLab Composer Repository
- GitLab Conan Repository
- GitLab Maven Repository
- GitLab NPM Registry
- GitLab NuGet Repository
- GitLab PyPi Repository
- API Docs
- API resources
- .gitignore API
- GitLab CI YMLs API
- Group and project access requests API
- Appearance API
- Applications API
- Audit Events API
- Avatar API
- Award Emoji API
- Project badges API
- Group badges API
- Branches API
- Broadcast Messages API
- Project clusters API
- Group clusters API
- Instance clusters API
- Commits API
- Container Registry API
- Custom Attributes API
- Dashboard annotations API
- Dependencies API
- Deploy Keys API
- Deployments API
- Discussions API
- Dockerfiles API
- Environments API
- Epics API
- Events
- Feature Flags API
- Feature flag user lists API
- Freeze Periods API
- Geo Nodes API
- Group Activity Analytics API
- Groups API
- Import API
- Issue Boards API
- Group Issue Boards API
- Issues API
- Epic Issues API
- Issues Statistics API
- Jobs API
- Keys API
- Labels API
- Group Labels API
- License
- Licenses API
- Issue links API
- Epic Links API
- Managed Licenses API
- Markdown API
- Group and project members API
- Merge request approvals API
- Merge requests API
- Project milestones API
- Group milestones API
- Namespaces API
- Notes API
- Notification settings API
- Packages API
- Pages domains API
- Pipeline schedules API
- Pipeline triggers API
- Pipelines API
- Project Aliases API
- Project import/export API
- Project repository storage moves API
- Project statistics API
- Project templates API
- Projects API
- Protected branches API
- Protected tags API
- Releases API
- Release links API
- Repositories API
- Repository files API
- Repository submodules API
- Resource label events API
- Resource milestone events API
- Resource weight events API
- Runners API
- SCIM API
- Search API
- Services API
- Application settings API
- Sidekiq Metrics API
- Snippets API
- Project snippets
- Application statistics API
- Suggest Changes API
- System hooks API
- Tags API
- Todos API
- Users API
- Project-level Variables API
- Group-level Variables API
- Version API
- Vulnerabilities API
- Vulnerability Findings API
- Wikis API
- GraphQL API
- Getting started with GitLab GraphQL API
- GraphQL API Resources
- API V3 to API V4
- Validate the .gitlab-ci.yml (API)
- User Docs
- Abuse reports
- User account
- Active sessions
- Deleting a User account
- Permissions
- Personal access tokens
- Profile preferences
- Threads
- GitLab and SSH keys
- GitLab integrations
- Git
- GitLab.com settings
- Infrastructure as code with Terraform and GitLab
- GitLab keyboard shortcuts
- GitLab Markdown
- AsciiDoc
- GitLab Notification Emails
- GitLab Quick Actions
- Autocomplete characters
- Reserved project and group names
- Search through GitLab
- Advanced Global Search
- Advanced Syntax Search
- Time Tracking
- GitLab To-Do List
- Administrator Docs
- Reference architectures
- Reference architecture: up to 1,000 users
- Reference architecture: up to 2,000 users
- Reference architecture: up to 3,000 users
- Reference architecture: up to 5,000 users
- Reference architecture: up to 10,000 users
- Reference architecture: up to 25,000 users
- Reference architecture: up to 50,000 users
- Troubleshooting a reference architecture set up
- Working with the bundled Consul service
- Configuring PostgreSQL for scaling
- Configuring GitLab application (Rails)
- Load Balancer for multi-node GitLab
- Configuring a Monitoring node for Scaling and High Availability
- NFS
- Working with the bundled PgBouncer service
- Configuring Redis for scaling
- Configuring Sidekiq
- Admin Area settings
- Continuous Integration and Deployment Admin settings
- Custom instance-level project templates
- Diff limits administration
- Enable and disable GitLab features deployed behind feature flags
- Geo nodes Admin Area
- GitLab Pages administration
- Health Check
- Job logs
- Labels administration
- Log system
- PlantUML & GitLab
- Repository checks
- Repository storage paths
- Repository storage types
- Account and limit settings
- Service templates
- System hooks
- Changing your time zone
- Uploads administration
- Abuse reports
- Activating and deactivating users
- Audit Events
- Blocking and unblocking users
- Broadcast Messages
- Elasticsearch integration
- Gitaly
- Gitaly Cluster
- Gitaly reference
- Monitoring GitLab
- Monitoring GitLab with Prometheus
- Performance Bar
- Usage statistics
- Object Storage
- Performing Operations in GitLab
- Cleaning up stale Redis sessions
- Fast lookup of authorized SSH keys in the database
- Filesystem Performance Benchmarking
- Moving repositories managed by GitLab
- Run multiple Sidekiq processes
- Sidekiq MemoryKiller
- Switching to Puma
- Understanding Unicorn and unicorn-worker-killer
- User lookup via OpenSSH's AuthorizedPrincipalsCommand
- GitLab Package Registry administration
- GitLab Container Registry administration
- Replication (Geo)
- Geo database replication
- Geo with external PostgreSQL instances
- Geo configuration
- Using a Geo Server
- Updating the Geo nodes
- Geo with Object storage
- Docker Registry for a secondary node
- Geo for multiple nodes
- Geo security review (Q&A)
- Location-aware Git remote URL with AWS Route53
- Tuning Geo
- Removing secondary Geo nodes
- Geo data types support
- Geo Frequently Asked Questions
- Geo Troubleshooting
- Geo validation tests
- Disaster Recovery (Geo)
- Disaster recovery for planned failover
- Bring a demoted primary node back online
- Automatic background verification
- Rake tasks
- Back up and restore GitLab
- Clean up
- Namespaces
- Maintenance Rake tasks
- Geo Rake Tasks
- GitHub import
- Import bare repositories
- Integrity check Rake task
- LDAP Rake tasks
- Listing repository directories
- Praefect Rake tasks
- Project import/export administration
- Repository storage Rake tasks
- Generate sample Prometheus data
- Uploads migrate Rake tasks
- Uploads sanitize Rake tasks
- User management
- Webhooks administration
- X.509 signatures
- Server hooks
- Static objects external storage
- Updating GitLab
- GitLab release and maintenance policy
- Security
- Password Storage
- Custom password length limits
- Restrict allowed SSH key technologies and minimum length
- Rate limits
- Webhooks and insecure internal web services
- Information exclusivity
- How to reset your root password
- How to unlock a locked user from the command line
- User File Uploads
- How we manage the TLS protocol CRIME vulnerability
- User email confirmation at sign-up
- Security of running jobs
- Proxying assets
- CI/CD Environment Variables
- Contributor and Development Docs
- Contribute to GitLab
- Community members & roles
- Implement design & UI elements
- Issues workflow
- Merge requests workflow
- Code Review Guidelines
- Style guides
- GitLab Architecture Overview
- CI/CD development documentation
- Database guides
- Database Review Guidelines
- Database Review Guidelines
- Migration Style Guide
- What requires downtime?
- Understanding EXPLAIN plans
- Rake tasks for developers
- Mass inserting Rails models
- GitLab Documentation guidelines
- Documentation Style Guide
- Documentation structure and template
- Documentation process
- Documentation site architecture
- Global navigation
- GitLab Docs monthly release process
- Telemetry Guide
- Usage Ping Guide
- Snowplow Guide
- Experiment Guide
- Feature flags in development of GitLab
- Feature flags process
- Developing with feature flags
- Feature flag controls
- Document features deployed behind feature flags
- Frontend Development Guidelines
- Accessibility & Readability
- Ajax
- Architecture
- Axios
- Design Patterns
- Frontend Development Process
- DropLab
- Emojis
- Filter
- Frontend FAQ
- GraphQL
- Icons and SVG Illustrations
- InputSetter
- Performance
- Principles
- Security
- Tooling
- Vuex
- Vue
- Geo (development)
- Geo self-service framework (alpha)
- Gitaly developers guide
- GitLab development style guides
- API style guide
- Go standards and style guidelines
- GraphQL API style guide
- Guidelines for shell commands in the GitLab codebase
- HTML style guide
- JavaScript style guide
- Migration Style Guide
- Newlines style guide
- Python Development Guidelines
- SCSS style guide
- Shell scripting standards and style guidelines
- Sidekiq debugging
- Sidekiq Style Guide
- SQL Query Guidelines
- Vue.js style guide
- Instrumenting Ruby code
- Testing standards and style guidelines
- Flaky tests
- Frontend testing standards and style guidelines
- GitLab tests in the Continuous Integration (CI) context
- Review Apps
- Smoke Tests
- Testing best practices
- Testing levels
- Testing Rails migrations at GitLab
- Testing Rake tasks
- End-to-end Testing
- Beginner's guide to writing end-to-end tests
- End-to-end testing Best Practices
- Dynamic Element Validation
- Flows in GitLab QA
- Page objects in GitLab QA
- Resource class in GitLab QA
- Style guide for writing end-to-end tests
- Testing with feature flags
- Translate GitLab to your language
- Internationalization for GitLab
- Translating GitLab
- Proofread Translations
- Merging translations from CrowdIn
- Value Stream Analytics development guide
- GitLab subscription
- Activate GitLab EE with a license