# Custom domains and SSL/TLS Certificates
> 原文：[https://docs.gitlab.com/ee/user/project/pages/custom_domains_ssl_tls_certification/](https://docs.gitlab.com/ee/user/project/pages/custom_domains_ssl_tls_certification/)
* [Set up Pages with a custom domain](#set-up-pages-with-a-custom-domain)
* [Requirements](#requirements)
* [Steps](#steps)
* [1\. Add a custom domain to Pages](#1-add-a-custom-domain-to-pages)
* [2\. Get the verification code](#2-get-the-verification-code)
* [3\. Set up DNS records for Pages](#3-set-up-dns-records-for-pages)
* [For root domains](#for-root-domains)
* [For subdomains](#for-subdomains)
* [For both root and subdomains](#for-both-root-and-subdomains)
* [4\. Verify the domain’s ownership](#4-verify-the-domains-ownership)
* [Troubleshooting Pages domain verification](#troubleshooting-pages-domain-verification)
* [Adding more domain aliases](#adding-more-domain-aliases)
* [Redirecting `www.domain.com` to `domain.com` with Cloudflare](#redirecting-wwwdomaincom-to-domaincom-with-cloudflare)
* [Adding an SSL/TLS certificate to Pages](#adding-an-ssltls-certificate-to-pages)
* [Requirements](#requirements-1)
* [Steps](#steps-1)
* [Force HTTPS for GitLab Pages websites](#force-https-for-gitlab-pages-websites)
# Custom domains and SSL/TLS Certificates[](#custom-domains-and-ssltls-certificates "Permalink")
使用自定義域設置 GitLab 頁面，并向其中添加 SSL / TLS 證書，是 GitLab 頁面的可選功能.
要將一個或多個自定義域名用于您的 Pages 網站，您可以：
* 添加[自定義**根域**或**子域**](#set-up-pages-with-a-custom-domain) .
* Add [SSL/TLS certification](#adding-an-ssltls-certificate-to-pages).
## Set up Pages with a custom domain[](#set-up-pages-with-a-custom-domain "Permalink")
要使用自定義域名設置頁面，請閱讀以下要求和步驟.
### Requirements[](#requirements "Permalink")
* 在默認的 Pages 域（ `*.gitlab.io` ，對于 GitLab.com）下運行的 GitLab Pages 網站已啟動并正在運行.
* 自定義域名`example.com`或子`subdomain.example.com` .
* 訪問您域的服務器控制面板以設置 DNS 記錄：
* 將您的域指向 GitLab Pages 服務器的 DNS A 或 CNAME 記錄.
* DNS TXT 記錄以驗證您的域的所有權.
### Steps[](#steps "Permalink")
請按照以下步驟將您的自定義域添加到 Pages. 另請參閱本文檔，以獲取[有關 DNS 記錄](dns_concepts.html)的[概述](dns_concepts.html) .
#### 1\. Add a custom domain to Pages[](#1-add-a-custom-domain-to-pages "Permalink")
導航到項目的" **設置">"頁面"** ，然后單擊" **+新域"**將自定義域添加到 GitLab 頁面. 您可以選擇是否：
* Add an [SSL/TLS certificate](#adding-an-ssltls-certificate-to-pages).
* 保留為空白（以后可以添加）.
Click **建立新網域**.
[](img/add_certificate_to_pages.png)
#### 2\. Get the verification code[](#2-get-the-verification-code "Permalink")
將新域添加到 Pages 后，系統將提示您輸入驗證碼. 從 GitLab 復制值，并將其作為下一步的 TXT 記錄粘貼到您域的控制面板中.
[](img/get_domain_verification_code_v12_0.png)
#### 3\. Set up DNS records for Pages[](#3-set-up-dns-records-for-pages "Permalink")
閱讀本文檔以[獲取 Pages 的 DNS 記錄概述](dns_concepts.html) . 如果您熟悉此主題，請根據您要與 Pages 網站一起使用的域類型，按照以下說明進行操作：
* [For root domains](#for-root-domains), `example.com`.
* [For subdomains](#for-subdomains), `subdomain.example.com`.
* [For both](#for-both-root-and-subdomains).
**注意：**您可以[在自管實例上配置 IPv6](../../../../administration/pages/index.html#advanced-configuration) ，但是 GitLab.com 上的 Pages 當前未配置 IPv6\. 有關詳細信息，請關注[此問題](https://gitlab.com/gitlab-org/gitlab/-/issues/214718) .
##### For root domains[](#for-root-domains "Permalink")
根域（ `example.com` ）要求：
* 指向您的域指向 Pages 服務器的[DNS A 記錄](dns_concepts.html#a-record) .
* [TXT 記錄](dns_concepts.html#txt-record)以驗證您的域的所有權.
| From | DNS 記錄 | To |
| --- | --- | --- |
| `example.com` | A | `35.185.44.232` |
| `_gitlab-pages-verification-code.example.com` | TXT | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
對于 GitLab.com 上的項目，此 IP 為`35.185.44.232` . 對于位于其他 GitLab 實例（CE 或 EE）中的項目，請聯系您的系統管理員以詢問此信息（該 IP 地址是實例上運行的 Pages 服務器）.
[](img/dns_add_new_a_record_example_updated_2018.png)
**注意：**請注意，如果**僅**將根域用于 GitLab Pages 網站，并且域注冊商支持此功能，則可以添加 DNS 頂點`CNAME`記錄而不是`A`記錄. 這樣做的主要優點是，當 GitLab.com 上的 GitLab Pages IP 出于任何原因更改時，您無需更新`A`記錄. 可能會有一些例外，但是**不建議使用此方法，**因為如果您為根域設置[`MX`記錄](dns_concepts.html#mx-record) ，則**該方法**很可能不起作用.
##### For subdomains[](#for-subdomains "Permalink")
子域（ `subdomain.example.com` ）要求：
* 將您的子域指向 Pages 服務器的 DNS [CNAME 記錄](dns_concepts.html#cname-record)記錄.
* DNS [TXT 記錄](dns_concepts.html#txt-record)以驗證您的域的所有權.
| From | DNS 記錄 | To |
| --- | --- | --- |
| `subdomain.example.com` | CNAME | `namespace.gitlab.io` |
| `_gitlab-pages-verification-code.subdomain.example.com` | TXT | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
請注意，無論是用戶網站還是項目網站， `CNAME`都應指向您的 Pages 域（ `namespace.gitlab.io` ），而不包含任何`/project-name` .
[](img/dns_cname_record_example.png)
##### For both root and subdomains[](#for-both-root-and-subdomains "Permalink")
在某些情況下，您需要將子域和根域都指向同一個網站，例如`example.com`和`www.example.com` .
他們要求：
* 域的 DNS A 記錄.
* 子域的 DNS CNAME 記錄.
* 每個 DNS TXT 記錄.
| From | DNS 記錄 | To |
| --- | --- | --- |
| `example.com` | A | `35.185.44.232` |
| `_gitlab-pages-verification-code.example.com` | TXT | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
| `www.example.com` | CNAME | `namespace.gitlab.io` |
| `_gitlab-pages-verification-code.www.example.com` | TXT | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
如果您使用的是 CloudFlare，請選中[使用 Cloudflare 將`www.domain.com`重定向到`domain.com`](#redirecting-wwwdomaincom-to-domaincom-with-cloudflare) .
> **Notes**:
>
> * 如果要將`domain.com`指向 GitLab Pages 網站，請**不要**使用 CNAME 記錄. 請改用`A`記錄.
> * **不要**在默認的 Pages 域之后添加任何特殊字符. 例如，不要將`subdomain.domain.com`指向或`namespace.gitlab.io/` . 但是，某些域托管服務提供商可能會請求結尾點（ `namespace.gitlab.io.` ）.
> * GitLab.com 上的 GitLab Pages IP 在 2017 年[進行了更改](https://about.gitlab.com/releases/2017/03/06/we-are-changing-the-ip-of-gitlab-pages-on-gitlab-com/) .
> * GitLab.com [上的](https://about.gitlab.com/blog/2018/07/19/gcp-move-update/#gitlab-pages-and-custom-domains) GitLab Pages IP `35.185.44.232` 2018 年的 52.167.214.135 [更改](https://about.gitlab.com/blog/2018/07/19/gcp-move-update/#gitlab-pages-and-custom-domains)為`52.167.214.135` .
#### 4\. Verify the domain’s ownership[](#4-verify-the-domains-ownership "Permalink")
添加所有 DNS 記錄后：
1. 返回項目的**設置>頁面** .
2. 找到您的域名，然后單擊" **詳細信息"** .
3. 點擊**重試驗證**按鈕以激活您的新域.
[](img/retry_domain_verification_v12_0.png)
一旦您的域名啟用，您的網站就會通過您的域名可用.
**注意：**考慮到啟用了域驗證的 GitLab 實例，如果該域不能在 7 天之內得到驗證，它將被從 GitLab 項目中刪除.
> **Notes:**
>
> * **GitLab.com 用戶必須進行**域驗證； 對于 GitLab 自管實例，您的 GitLab 管理員可以選擇[禁用自定義域驗證](../../../../administration/pages/index.html#custom-domain-verification) .
> * [DNS 傳播可能需要一些時間（最多 24 小時）](https://www.inmotionhosting.com/support/domain-names/dns-nameserver-changes/domain-names-dns-changes/) ，盡管通常只需幾分鐘即可完成. 否則，驗證將失敗，并且嘗試訪問您的域的嘗試將以 404 響應.
> * 驗證您的域后，請保留驗證記錄：您的域將定期重新驗證，如果刪除該記錄，則可能會被禁用.
##### Troubleshooting Pages domain verification[](#troubleshooting-pages-domain-verification "Permalink")
要手動驗證您已正確配置了域驗證`TXT` DNS 條目，可以在終端中運行以下命令：
```
dig _gitlab-pages-verification-code.<YOUR-PAGES-DOMAIN> TXT
```
期望輸出：
```
;; ANSWER SECTION:
_gitlab-pages-verification-code.<YOUR-PAGES-DOMAIN>. 300 IN TXT "gitlab-pages-verification-code=<YOUR-VERIFICATION-CODE>"
```
### Adding more domain aliases[](#adding-more-domain-aliases "Permalink")
You can add more than one alias (custom domains and subdomains) to the same project. An alias can be understood as having many doors leading to the same room.
您為網站設置的所有別名都將在" **設置">"頁面"**上列出. 在該頁面上，您可以查看，添加和刪除它們.
### Redirecting `www.domain.com` to `domain.com` with Cloudflare[](#redirecting-wwwdomaincom-to-domaincom-with-cloudflare "Permalink")
如果您使用 Cloudflare，則可以將`www`重定向到`domain.com`而無需同時將`www.domain.com`和`domain.com`添加到 GitLab.
為此，您可以使用與 CNAME 記錄關聯的 Cloudflare 的頁面規則將`www.domain.com`重定向到`domain.com` . 您可以使用以下設置：
1. 在 Cloudflare 中，創建一個 DNS `A`記錄，將`domain.com`指向`35.185.44.232` .
2. 在 GitLab 中，將域添加到 GitLab 頁面中并獲取驗證碼.
3. 在 Cloudflare 中，創建 DNS `TXT`記錄以驗證您的域.
4. 在 GitLab 中，驗證您的域.
5. 在 Cloudflare 中，創建將`www`指向`domain.com`的 DNS `CNAME`記錄.
6. 在 Cloudflare 中，添加將`www.domain.com`指向`domain.com`的頁面規則：
* 導航到您域的信息中心，然后點擊頂部導航欄中的**頁面規則** .
* 單擊**創建頁面規則** .
* 輸入域名`www.domain.com` ，然后點擊**+添加設置** .
* 從下拉菜單中，選擇**轉發 URL** ，然后選擇狀態代碼**301-永久重定向** .
* 輸入目標網址`https://domain.com` .
## Adding an SSL/TLS certificate to Pages[](#adding-an-ssltls-certificate-to-pages "Permalink")
閱讀本文檔以獲取[有關 SSL / TLS 認證](ssl_tls_concepts.html)的[概述](ssl_tls_concepts.html) .
要使用 GitLab 頁面保護您的自定義域，您可以選擇：
* 使用[Let's Encrypt 與 GitLab Pages 的集成](lets_encrypt_integration.html) ，該[集成](lets_encrypt_integration.html)會自動獲取和續訂您 Pages 域的 SSL 證書.
* 遵循以下步驟，將 SSL / TLS 證書手動添加到 GitLab Pages 網站.
### Requirements[](#requirements-1 "Permalink")
* 可通過自定義域訪問 GitLab Pages 網站并正在運行.
* **PEM 證書** ：它是由 CA 生成的證書，需要將其添加到字段**Certificate（PEM）中** .
* **[中間證書](https://en.wikipedia.org/wiki/Intermediate_certificate_authority)** ：（也稱為"根證書"），它是標識 CA 的加密密鑰鏈的一部分. 通常，它與 PEM 證書結合在一起，但是在某些情況下，您需要手動添加它們. [CloudFlare 證書](https://about.gitlab.com/blog/2017/02/07/setting-up-gitlab-pages-with-cloudflare-certificates/)就是其中一種.
* **私鑰** ，這是一個加密密鑰，可根據您的域驗證您的 PEM.
### Steps[](#steps-1 "Permalink")
* 要在添加新域時添加證書，請轉至項目的**"設置">"頁面">"新域"** ，添加域名和證書.
* 要將證書添加到先前添加的域中，請轉到項目的**"設置">"頁面"** ，找到您的域名，單擊" **詳細信息"**和" **編輯"**以添加證書.
[](img/add_certificate_to_pages.png)
1. 將 PEM 證書添加到其相應的字段.
2. 如果您的證書缺少中間證書，請復制并粘貼根證書（通常可從您的 CA 網站獲得），然后將其粘貼到[與 PEM 證書相同的字段中](https://about.gitlab.com/blog/2017/02/07/setting-up-gitlab-pages-with-cloudflare-certificates/) ，只需在它們之間跳過一行即可.
3. 復制您的私鑰并將其粘貼到最后一個字段中.
**注意：** **請勿**在常規文本編輯器中打開證書或加密密鑰. 始終使用代碼編輯器（例如 Sublime Text，Atom，Dreamweaver，括號等）.
## Force HTTPS for GitLab Pages websites[](#force-https-for-gitlab-pages-websites "Permalink")
在 GitLab 10.7 中[引入](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/28857) .
為了使您的網站訪問者更加安全，您可以選擇對 GitLab 頁面強制使用 HTTPS. 這樣，所有通過 HTTP 訪問您的網站的嘗試都會通過 301 自動重定向到 HTTPS.
它既可以與 GitLab 的默認域一起使用，也可以與您的自定義域一起使用（只要您為其設置了有效的證書）.
要啟用此設置：
1. 導航到項目的**"設置">"頁面"** .
2. 選中" **強制 HTTPS** "復選框**（需要有效的證書）** .
**注意：**如果在 GitLab 頁面前面使用 CloudFlare CDN，請確保將 SSL 連接設置設置為`full`而不是`flexible` . 有關更多詳細信息，請參閱[CloudFlare CDN 指導](https://support.cloudflare.com/hc/en-us/articles/200170416-End-to-end-HTTPS-with-Cloudflare-Part-3-SSL-options#h_4e0d1a7c-eb71-4204-9e22-9d3ef9ef7fef) .
- 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