# Replication (Geo)
> 原文：[https://docs.gitlab.com/ee/administration/geo/replication/](https://docs.gitlab.com/ee/administration/geo/replication/)
* [Overview](#overview)
* [Use cases](#use-cases)
* [How it works](#how-it-works)
* [Architecture](#architecture)
* [Requirements for running Geo](#requirements-for-running-geo)
* [Firewall rules](#firewall-rules)
* [LDAP](#ldap)
* [Geo Tracking Database](#geo-tracking-database)
* [Geo Log Cursor](#geo-log-cursor)
* [Setup instructions](#setup-instructions)
* [Using Omnibus GitLab](#using-omnibus-gitlab)
* [Post-installation documentation](#post-installation-documentation)
* [Configuring Geo](#configuring-geo)
* [Updating Geo](#updating-geo)
* [Pausing and resuming replication](#pausing-and-resuming-replication)
* [Configuring Geo for multiple nodes](#configuring-geo-for-multiple-nodes)
* [Configuring Geo with Object Storage](#configuring-geo-with-object-storage)
* [Disaster Recovery](#disaster-recovery)
* [Replicating the Container Registry](#replicating-the-container-registry)
* [Security Review](#security-review)
* [Tuning Geo](#tuning-geo)
* [Set up a location-aware Git URL](#set-up-a-location-aware-git-url)
* [Remove Geo node](#remove-geo-node)
* [Disable Geo](#disable-geo)
* [Current limitations](#current-limitations)
* [Limitations on replication/verification](#limitations-on-replicationverification)
* [Frequently Asked Questions](#frequently-asked-questions)
* [Log files](#log-files)
* [Troubleshooting](#troubleshooting)
# Replication (Geo)[](#replication-geo-premium-only "Permalink")
版本历史
* 在 GitLab 企业版 8.9 中引入.
* 与组合使用地理[多节点架构](../../reference_architectures/index.html)在考虑**一般可用** （GA） [GitLab 高级](https://about.gitlab.com/pricing/) 10.4\.
使用 Geo 复制是广泛分布的开发团队的解决方案.
## Overview[](#overview "Permalink")
对于远离单个 GitLab 实例的团队而言，获取大型存储库可能需要很长时间.
Geo 提供您的 GitLab 实例的本地只读实例. 这样可以减少克隆和获取大型存储库所需的时间，从而加快开发速度.
**注意：**在设置 Geo 之前，请仔细检查[要求](#requirements-for-running-geo) .
有关 Geo 的视频介绍，请参见[GitLab Geo-GitLab 功能介绍](https://www.youtube.com/watch?v=-HDLxSjEh6w) .
**注意：**从发布到发布，Geo 进行了重大更改. **支持**升级和[记录](#updating-geo) ，但你应该确保您使用的文件的正确的版本进行安装.
为确保您使用的文档版本正确，请[在 GitLab.com 上](https://gitlab.com/gitlab-org/gitlab/blob/master/doc/administration/geo/replication/index.md)导航[至此页面的源版本](https://gitlab.com/gitlab-org/gitlab/blob/master/doc/administration/geo/replication/index.md) ，然后从**Switch 分支/标签**下拉列表中选择适当的版本. 例如， [`v11.2.3-ee`](https://gitlab.com/gitlab-org/gitlab/blob/v11.2.3-ee/doc/administration/geo/replication/index.md) .
## Use cases[](#use-cases "Permalink")
实施 Geo 具有以下好处：
* 将分布式开发人员克隆和获取大型存储库和项目所需的时间从几分钟减少到几秒钟.
* 无论您身在何处，都可以使所有开发人员共同贡献想法并并行工作.
* 平衡**主**节点和**辅助**节点之间的只读负载.
此外，它：
* 除读取 GitLab Web 界面中可用的任何数据外，还可用于克隆和获取项目（请参阅[当前限制](#current-limitations) ）.
* 克服远程办公室之间的慢速连接，通过提高分布式团队的速度来节省时间.
* 帮助减少自动任务，自定义集成和内部工作流程的加载时间.
* 可以在[灾难恢复](../disaster_recovery/index.html)方案中快速故障转移到**辅助**节点.
* 允许[计划的故障转移](../disaster_recovery/planned_failover.html)到**辅助**节点.
地理位置提供：
* 只读**辅助**节点：维护一个**主** GitLab 节点，同时仍为每个分布式团队启用只读**辅助**节点.
* 身份验证系统挂钩： **辅助**节点从**主**实例接收所有身份验证数据（例如用户帐户和登录名）.
* 直观的用户界面： **辅助**节点使用团队已习惯的相同 Web 界面. 此外，还有可视通知会阻止写操作，并清楚表明用户在**辅助**节点上.
## How it works[](#how-it-works "Permalink")
除了读取任何数据外，您的 Geo 实例还可用于克隆和获取项目. 这将使在较大距离上使用大型存储库的速度更快.
[](img/geo_overview.png)
启用地理位置后，：
* 原始实例称为**主要**节点.
* 复制的只读节点称为**辅助**节点.
请记住：
* **辅助**节点与**主**节点对话以：
* 获取用于登录的用户数据（API）.
* 复制存储库，LFS 对象和附件（HTTPS + JWT）.
* 从 GitLab Premium 10.0 开始， **主**节点不再与**辅助**节点对话以通知更改（API）.
* [GitLab Premium](https://about.gitlab.com/pricing/#self-managed) 11.3 中[引入](https://about.gitlab.com/releases/2018/09/22/gitlab-11-3-released/)了直接推送到**辅助**节点（对于 HTTP 和 SSH，包括 Git LFS）.
* 当前的实施存在[局限性](#current-limitations) .
### Architecture[](#architecture "Permalink")
下图说明了 Geo 的基础体系结构.
[](img/geo_architecture.png)
在此图中：
* 有**主**节点和一个**辅助**节点的详细信息.
* 只能在**主**节点上执行对数据库的写入. **辅助**节点通过 PostgreSQL 流复制接收数据库更新.
* 如果存在，则应将[LDAP 服务器](#ldap)配置为针对[灾难恢复](../disaster_recovery/index.html)方案进行复制.
* **辅助**节点使用受 JWT 保护的特殊授权对**主要**节点执行不同类型的同步：
* 存储库是通过 HTTPS 上的 Git 克隆/更新的.
* 使用专用 API 端点通过 HTTPS 下载附件，LFS 对象和其他文件.
从用户执行 Git 操作的角度来看：
* **主**节点的行为就像一个完整的读写 GitLab 实例.
* **辅助**节点是只读的，但代理 Git 将操作推送到**主**节点. 这使得**辅助**节点似乎本身就支持推送操作.
为了简化该图，省略了一些必要的组件. 注意：
* SSH 上的 Git 需要[`gitlab-shell`](https://gitlab.com/gitlab-org/gitlab-shell)和 OpenSSH.
* 通过 HTTPS 进行 Git 时需要[`gitlab-workhorse`](https://gitlab.com/gitlab-org/gitlab-workhorse) .
请注意， **辅助**节点需要两个不同的 PostgreSQL 数据库：
* 一个只读数据库实例，用于从 GitLab 主数据库中流式传输数据.
* **辅助**节点在内部使用的[另一个数据库实例](#geo-tracking-database)记录已复制的数据.
在**辅助**节点中，还有一个附加的守护进程： [Geo Log Cursor](#geo-log-cursor) .
## Requirements for running Geo[](#requirements-for-running-geo "Permalink")
要运行 Geo，必须具备以下条件：
* 支持 OpenSSH 6.9+的操作系统（需要[在数据库中快速查找授权的 SSH 密钥](../../operations/fast_ssh_key_lookup.html) ）当前已知版本的 OpenSSH 随附了以下操作系统：
* [CentOS](https://www.centos.org) 7.4 以上
* [Ubuntu](https://ubuntu.com) 16.04 以上
* PostgreSQL 11+ with [FDW](https://s0www0postgresql0org.icopy.site/docs/11/postgres-fdw.html) support and [Streaming Replication](https://wiki.postgresql.org/wiki/Streaming_Replication)
* 转到 2.9+
* 所有节点必须运行相同的 GitLab 版本.
此外，请检查 GitLab 的[最低要求](../../../install/requirements.html) ，我们建议您使用：
* 至少具有 GitLab 企业版 10.0 的基本地理功能.
* 最新版本以获得更好的体验.
### Firewall rules[](#firewall-rules "Permalink")
下表列出了在 Geo 的**主**节点和**辅助**节点之间必须打开的基本端口.
| **Primary** node | **Secondary** node | Protocol |
| --- | --- | --- |
| 80 | 80 | HTTP |
| 443 | 443 | TCP 或 HTTPS |
| 22 | 22 | TCP |
| 5432 | | PostgreSQL |
在[Package 默认值中](https://docs.gitlab.com/omnibus/package-information/defaults.html)查看 GitLab 使用的端口的完整列表
**注意：** [Web 终端](../../../ci/environments/index.html#web-terminals)支持要求您的负载平衡器正确处理 WebSocket 连接. 当使用 HTTP 或 HTTPS 代理，负载平衡器必须被配置为通过`Connection`和`Upgrade`逐跳头. 有关更多详细信息，请参见[Web 终端](../../integration/terminal.html)集成指南.**注意：**将 HTTPS 协议用于端口 443 时，您需要向负载均衡器添加 SSL 证书. 如果您想在 GitLab 应用程序服务器上终止 SSL，请使用 TCP 协议.
### LDAP[](#ldap "Permalink")
We recommend that if you use LDAP on your **primary** node, you also set up secondary LDAP servers on each **secondary** node. Otherwise, users will not be able to perform Git operations over HTTP(s) on the **secondary** node using HTTP Basic Authentication. However, Git via SSH and personal access tokens will still work.
**注意：**所有**辅助**节点都可以共享 LDAP 服务器，但是额外的延迟可能是一个问题. 另外，如果将**辅助**节点提升为**主要**节点，请考虑在[灾难恢复](../disaster_recovery/index.html)方案中将使用哪些 LDAP 服务器.
查看有关如何在 LDAP 服务中设置复制的说明. 根据使用的软件或服务，说明会有所不同. 例如，OpenLDAP 提供了[这些说明](https://www.openldap.org/doc/admin24/replication.html) .
### Geo Tracking Database[](#geo-tracking-database "Permalink")
跟踪数据库实例用作元数据，以控制需要在本地实例的磁盘上更新的内容. 例如：
* 下载新资产.
* 提取新的 LFS 对象.
* 从最近更新的存储库中获取更改.
因为复制的数据库实例是只读的，所以每个**辅助**节点都需要这个额外的数据库实例. 跟踪数据库需要`postgres_fdw`扩展名.
### Geo Log Cursor[](#geo-log-cursor "Permalink")
该守护程序：
* 读取由**主**节点复制到**辅助**数据库实例的事件的日志.
* 使用需要执行的更改更新地理跟踪数据库实例.
在跟踪数据库实例中将某些内容标记为要更新时，在**辅助**节点上运行的异步作业将执行所需的操作并更新状态.
这种新的体系结构使 GitLab 能够应对节点之间的连接问题. **辅助**节点与**主**节点断开连接的时间无关紧要，因为它将能够以正确的顺序重放所有事件并再次与**主**节点同步.
## Setup instructions[](#setup-instructions "Permalink")
这些说明假定您有一个 GitLab 的工作实例. 他们指导您：
1. 将现有实例设为**主要**节点.
2. Adding **secondary** nodes.
**Caution:** The steps below should be followed in the order they appear. **确保所有节点上的 GitLab 版本均相同.**
### Using Omnibus GitLab[](#using-omnibus-gitlab "Permalink")
如果您使用 Omnibus 软件包安装了 GitLab（强烈建议）：
1. 在将用作**辅助**节点的服务器上[安装 GitLab 企业版](https://about.gitlab.com/install/) . 不要创建帐户或登录到新的**辅助**节点.
2. 在**主**节点上[载 GitLab 许可](../../../user/admin_area/license.html)以解锁 Geo. 该许可证必须适用于[GitLab Premium](https://about.gitlab.com/pricing/)或更高版本.
3. [Set up the database replication](database.html) (`primary (read-write) <-> secondary (read-only)` topology).
4. [在数据库中配置快速查找授权的 SSH 密钥](../../operations/fast_ssh_key_lookup.html) . 此步骤是必需的，并且必须**同时**在**主**节点和**辅助**节点上完成.
5. [配置 GitLab](configuration.html)以设置**主**节点和**辅助**节点.
6. 可选：为**辅助**节点[配置辅助 LDAP 服务器](../../auth/ldap/index.html) . 请参阅[LDAP 上的注释](#ldap) .
7. [Follow the “Using a Geo Server” guide](using_a_geo_server.html).
## Post-installation documentation[](#post-installation-documentation "Permalink")
在**辅助**节点上安装 GitLab 并执行初始配置后，请参阅以下文档以获取安装后信息.
### Configuring Geo[](#configuring-geo "Permalink")
有关配置 Geo 的信息，请参见[Geo 配置](configuration.html) .
### Updating Geo[](#updating-geo "Permalink")
有关如何将 Geo 节点更新到最新的 GitLab 版本的信息，请参见[更新 Geo 节点](updating_the_geo_nodes.html) .
### Pausing and resuming replication[](#pausing-and-resuming-replication "Permalink")
[Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/35913) in [GitLab Premium](https://about.gitlab.com/pricing/) 13.2.
在某些情况下，例如在[升级](updating_the_geo_nodes.html)或[计划的故障转移](../disaster_recovery/planned_failover.html)期间，最好暂停主数据库和辅助数据库之间的复制.
暂停和恢复复制是通过辅助节点上的命令行工具完成的.
**暂停：（从中学开始）**
```
gitlab-ctl geo-replication-pause
```
**恢复：（从中学开始）**
```
gitlab-ctl geo-replication-resume
```
### Configuring Geo for multiple nodes[](#configuring-geo-for-multiple-nodes "Permalink")
有关为多个节点配置 Geo 的信息，请参阅[针对多个服务器的 Geo](multiple_servers.html) .
### Configuring Geo with Object Storage[](#configuring-geo-with-object-storage "Permalink")
有关配置带对象存储的 Geo 的信息，请参阅[带对象存储的 Geo](object_storage.html) .
### Disaster Recovery[](#disaster-recovery "Permalink")
有关在灾难恢复情况下使用 Geo 减轻数据丢失和恢复服务的信息，请参阅[灾难恢复](../disaster_recovery/index.html) .
### Replicating the Container Registry[](#replicating-the-container-registry "Permalink")
有关如何复制 Container Registry 的更多信息，请参阅[**辅助**节点的 Docker Registry](docker_registry.html) .
### Security Review[](#security-review "Permalink")
有关地理安全的更多信息，请参阅[地理安全审阅](security_review.html) .
### Tuning Geo[](#tuning-geo "Permalink")
有关调整 Geo 的更多信息，请参见[调整 Geo](tuning.html) .
### Set up a location-aware Git URL[](#set-up-a-location-aware-git-url "Permalink")
有关如何使用 AWS Route53 设置位置感知的 Git 远程 URL 的示例，请参阅使用 AWS Route53 [感知位置的 Git 远程 URL](location_aware_git_url.html) .
## Remove Geo node[](#remove-geo-node "Permalink")
For more information on removing a Geo node, see [Removing **secondary** Geo nodes](remove_geo_node.html).
## Disable Geo[](#disable-geo "Permalink")
要了解如何禁用地理位置，请参阅[禁用地理位置](disable_geo.html) .
## Current limitations[](#current-limitations "Permalink")
**注意：**此限制列表仅反映最新版本的 GitLab. 如果您使用的是旧版本，则可能存在其他限制.
* 将请求直接推送到**辅助**节点（对于 HTTP）或代理（对于 SSH）会将请求重定向到**主要**节点，而不是[直接处理它](https://gitlab.com/gitlab-org/gitlab/-/issues/1381) ，除非在 HTTP 中使用 Git over HTTP 并在 URI 中嵌入凭据. 例如， `https://user:password@secondary.tld` .
* 克隆，拉动或推送存在于**主**节点上但不存在于**辅助**节点上的存储库，这些存储库中的[选择性同步](configuration.html#selective-synchronization)不包括项目，因此不支持通过 SSH 进行， [但已计划进行支持](https://gitlab.com/groups/gitlab-org/-/epics/2562) . 支持 HTTP（S）.
* **主**节点必须在线才能进行 OAuth 登录. 现有会话和 Git 均不受影响. [正在计划](https://gitlab.com/gitlab-org/gitlab/-/issues/208465)支持**辅助**节点使用独立于主节点的 OAuth 提供程序.
* 安装过程需要执行多个手动步骤，根据具体情况，总共可能需要一个小时的时间. 我们正在努力改善这种体验. 有关详细信息，请参见[Omnibus GitLab 第 2978](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/2978)期.
* 问题/合并请求的实时更新（例如，通过长轮询）在**辅助**节点上不起作用.
* [选择性同步](configuration.html#selective-synchronization)仅适用于文件和存储库. 其他数据集已完全复制到**辅助**节点，使其不适合用作访问控制机制.
* 用于分支项目重复数据删除的对象池仅在**主**节点上工作，并在**辅助**节点上重复.
* [如果外部合并请求差异](../../merge_request_diffs.html)在磁盘上，则将不会复制它们，并且查看合并请求将失败. 但是，支持对象存储**中的**外部 MR 差异. 默认配置（数据库中）起作用.
* GitLab Runners 无法向**辅助**节点注册. [计划在将来](https://gitlab.com/gitlab-org/gitlab/-/issues/3294)对此提供支持.
### Limitations on replication/verification[](#limitations-on-replicationverification "Permalink")
您可以跟踪实现这些史诗/问题中缺少的项目的进度：
* [Unreplicated Data Types](https://gitlab.com/groups/gitlab-org/-/epics/893)
* [Verify all replicated data](https://gitlab.com/groups/gitlab-org/-/epics/1430)
这里有所有 GitLab [数据类型](datatypes.html)的完整列表以及[对复制和验证的现有支持](datatypes.html#limitations-on-replicationverification) .
## Frequently Asked Questions[](#frequently-asked-questions "Permalink")
有关常见问题的答案，请参见[地理位置常见问题解答](faq.html) .
## Log files[](#log-files "Permalink")
自 GitLab 9.5 起，Geo 将结构化日志消息存储在`geo.log`文件中. 对于 Omnibus 安装，此文件位于`/var/log/gitlab/gitlab-rails/geo.log` .
该文件包含有关 Geo 何时尝试同步存储库和文件的信息. 文件中的每一行都包含一个可以提取的单独的 JSON 条目. 例如，Elasticsearch 或 Splunk.
例如：
```
{"severity":"INFO","time":"2017-08-06T05:40:16.104Z","message":"Repository update","project_id":1,"source":"repository","resync_repository":true,"resync_wiki":true,"class":"Gitlab::Geo::LogCursor::Daemon","cursor_delay_s":0.038}
```
此消息表明，Geo 检测到项目`1`需要存储库更新.
## Troubleshooting[](#troubleshooting "Permalink")
有关故障排除步骤，请参阅[地理故障排除](troubleshooting.html) .
- 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