# Geo (development)
> 原文：[https://docs.gitlab.com/ee/development/geo.html](https://docs.gitlab.com/ee/development/geo.html)
* [Replication layer](#replication-layer)
* [Geo Log Cursor daemon](#geo-log-cursor-daemon)
* [Database replication](#database-replication)
* [Repository replication](#repository-replication)
* [Project Registry](#project-registry)
* [Repository Sync worker](#repository-sync-worker)
* [Uploads replication](#uploads-replication)
* [Upload Registry](#upload-registry)
* [File Download Dispatch worker](#file-download-dispatch-worker)
* [Authentication](#authentication)
* [Git Push to Geo secondary](#git-push-to-geo-secondary)
* [Using the Tracking Database](#using-the-tracking-database)
* [Configuration](#configuration)
* [Foreign Data Wrapper](#foreign-data-wrapper)
* [Refreshing the Foreign Tables](#refreshing-the-foreign-tables)
* [Accessing data from a Foreign Table](#accessing-data-from-a-foreign-table)
* [Finders](#finders)
* [Finders Performance](#finders-performance)
* [Redis](#redis)
* [Object Storage](#object-storage)
* [Verification](#verification)
* [Repository verification](#repository-verification)
* [Glossary](#glossary)
* [Primary node](#primary-node)
* [Secondary node](#secondary-node)
* [Streaming replication](#streaming-replication)
* [Tracking database](#tracking-database)
* [FDW](#fdw)
* [Geo Event Log](#geo-event-log)
* [Geo Log Cursor](#geo-log-cursor)
* [Code features](#code-features)
* [`Gitlab::Geo` utilities](#gitlabgeo-utilities)
* [Current node](#current-node)
* [Primary or secondary](#primary-or-secondary)
* [Geo Database configured?](#geo-database-configured)
* [Enablement](#enablement)
* [Read-only](#read-only)
* [Steps needed to replicate a new data type](#steps-needed-to-replicate-a-new-data-type)
* [Geo self-service framework (alpha)](#geo-self-service-framework-alpha)
* [History of communication channel](#history-of-communication-channel)
* [Custom code (GitLab 8.6 and earlier)](#custom-code-gitlab-86-and-earlier)
* [System hooks (GitLab 8.7 to 9.5)](#system-hooks-gitlab-87-to-95)
* [Geo Log Cursor (GitLab 10.0 and up)](#geo-log-cursor-gitlab-100-and-up)
* [Self-service framework](#self-service-framework)
# Geo (development)[](#geo-development-premium-only "Permalink")
Geo 将 GitLab 实例连接在一起. 一个 GitLab 实例被指定**为主**节点，并且可以与多个**辅助**节点一起运行. Geo 精心策划了很多组件，这些组件可以在下图中看到，并在本文档中进行了更详细的描述.
[](../administration/geo/replication/img/geo_architecture.png)
## Replication layer[](#replication-layer "Permalink")
Geo 处理不同组件的复制：
* [数据库](#database-replication) ：包括整个应用程序，缓存和作业除外.
* [Git 存储库](#repository-replication) ：包括项目和 Wiki.
* [上载的 Blob](#uploads-replication) ：包括从问题附带的图像到 CI 的原始日志和资产的所有内容.
除数据库复制外，在*辅助*节点上，所有内容均由[Geo Log Cursor](#geo-log-cursor)协调.
### Geo Log Cursor daemon[](#geo-log-cursor-daemon "Permalink")
[Geo Log Cursor 守护程序](#geo-log-cursor-daemon)是在每个**辅助**节点上运行的单独进程. 它监视[地理事件日志中](#geo-event-log)是否有新事件，并为每种特定事件类型创建后台作业.
例如，当更新存储库时，Geo **主**节点会创建一个带有关联的存储库更新事件的 Geo 事件. Geo Log Cursor 守护程序接收事件并安排一个`Geo::ProjectSyncWorker`作业，该作业将使用`Geo::RepositorySyncService`和`Geo::WikiSyncService`类分别更新存储库和 Wiki.
Geo Log Cursor 守护程序可以自动在高可用性模式下运行. 守护程序将不时尝试获取锁，一旦获得锁定，它将充当*活动*守护程序.
在同一节点上的所有其他正在运行的守护程序都将处于待机模式，如果*活动*守护程序释放其锁定，则可以恢复工作.
We use the [`ExclusiveLease`](https://www.rubydoc.info/github/gitlabhq/gitlabhq/Gitlab/ExclusiveLease) lock type with a small TTL, that is renewed at every pooling cycle. That allows us to implement this global lock with a timeout.
在池化周期结束时，如果守护程序无法更新和/或重新获得锁定，它将切换到待机模式.
### Database replication[](#database-replication "Permalink")
Geo 使用[流复制](#streaming-replication)将数据库从**主**节点[复制](#streaming-replication)到**辅助**节点. 通过此复制， **辅助**节点可以访问数据库中保存的所有数据. 因此，用户可以登录**次级**和读取所有的问题，合并请求等**辅助**节点上.
### Repository replication[](#repository-replication "Permalink")
Geo 还复制存储库. 每个**辅助**节点都[跟踪跟踪数据库](#tracking-database)中每个存储库的状态.
存在以下几种方式来复制存储库：
* [Repository Sync worker](#repository-sync-worker).
* [Geo Log Cursor](#geo-log-cursor).
#### Project Registry[](#project-registry "Permalink")
`Geo::ProjectRegistry`类定义用于跟踪存储库复制状态的模型. 对于主数据库中的每个项目，在跟踪数据库中保留一个记录.
它记录有关存储库的以下内容：
* 他们上次同步的时间.
* 上一次成功同步它们.
* 是否需要重新同步.
* 重试的时间.
* 重试次数.
* 是否以及何时进行验证.
它还将项目 Wiki 的这些属性存储在专用列中.
#### Repository Sync worker[](#repository-sync-worker "Permalink")
The `Geo::RepositorySyncWorker` class runs periodically in the background and it searches the `Geo::ProjectRegistry` model for projects that need updating. Those projects can be:
* 未同步：从未在**辅助**节点上同步过的项目，因此尚不存在.
* 最近更新：项目的`last_repository_updated_at`时间戳比`Geo::ProjectRegistry`模型中的`last_repository_successful_sync_at`时间戳更新.
* 手动：管理员可以在[地理管理面板中](../user/admin_area/geo_nodes.html)手动标记存储库以重新同步.
当我们在次要`RETRIES_BEFORE_REDOWNLOAD`时间内无法获取存储库时，Geo 会进行所谓的*重新下载* . 它将干净地克隆到存储根目录中的`@geo-temporary`目录中. 成功后，我们用新克隆的仓库替换主仓库.
### Uploads replication[](#uploads-replication "Permalink")
文件上传也被复制到**辅助**节点. 为了跟踪同步状态，使用了`Geo::UploadRegistry`模型.
#### Upload Registry[](#upload-registry "Permalink")
与[项目注册表](#project-registry)类似，有一个`Geo::UploadRegistry`模型可以跟踪同步的上传.
CI Job Artifacts and LFS objects are synced in a similar way as uploads, but they are tracked by `Geo::JobArtifactRegistry`, and `Geo::LfsObjectRegistry` models respectively.
#### File Download Dispatch worker[](#file-download-dispatch-worker "Permalink")
还类似于[Repository Sync 工作器](#repository-sync-worker) ，有一个`Geo::FileDownloadDispatchWorker`类，该类定期运行以同步所有尚未同步到 Geo **辅助**节点的上载.
通过 HTTP 复制文件，并通过`/api/v4/geo/transfers/:type/:id`端点（例如`/api/v4/geo/transfers/lfs/123` .
## Authentication[](#authentication "Permalink")
为了验证文件传输，每个`GeoNode`记录都有两个字段：
* 公共访问密钥（ `access_key`字段）.
* 秘密访问密钥（ `secret_access_key`字段）.
**次要**节点通过[JWT 请求进行](https://jwt.io/)身份验证. 当**辅助**节点希望下载文件时，它将发送带有`Authorization`标头的 HTTP 请求：
```
Authorization: GL-Geo <access_key>:<JWT payload>
```
**主**节点使用`access_key`字段查找相应的**辅助**节点并解密 JWT 有效负载，该负载包含用于标识文件请求的其他信息. 这样可以确保**辅助**节点为正确的数据库 ID 下载正确的文件. 例如，对于 LFS 对象，请求还必须包含文件的 SHA256 和. JWT 有效负载示例如下所示：
```
{ "data": { sha256: "31806bb23580caab78040f8c45d329f5016b0115" }, iat: "1234567890" }
```
如果请求的文件与请求的 SHA256 总和匹配，则 Geo **主**节点将通过[X-Sendfile](https://www.nginx.com/resources/wiki/start/topics/examples/xsendfile/)功能发送数据，这使 NGINX 可以处理文件传输而不会占用 Rails 或 Workhorse.
**注意：** JWT 需要在所涉及的机器之间同步时钟，否则它可能会因加密错误而失败.
## Git Push to Geo secondary[](#git-push-to-geo-secondary "Permalink")
Git Push Proxy 作为`gitlab-shell`组件内置的功能存在. 它仅在**辅助**节点上处于活动状态. 它允许从辅助节点克隆存储库的用户推送到相同的 URL.
定向到**次**节点的 Git `push`请求将发送到**主**节点，而`pull`请求将继续由**次**节点服务，以实现最大效率.
HTTPS 和 SSH 请求的处理方式不同：
* 使用 HTTPS，我们将为用户提供指向**主**节点上项目的`HTTP 302 Redirect` . Git 客户端足够聪明，可以理解该状态码并处理重定向.
* 使用 SSH，因为没有等效的方法来执行重定向，所以我们必须代理请求. 这是在[`gitlab-shell`](https://gitlab.com/gitlab-org/gitlab-shell)内部[`gitlab-shell`](https://gitlab.com/gitlab-org/gitlab-shell) ，方法是先将请求转换为 HTTP 协议，然后将其代理到**主**节点.
[`gitlab-shell`](https://gitlab.com/gitlab-org/gitlab-shell)守护程序根据`/api/v4/allowed`的响应知道何时进行代理. 返回一个特殊的`HTTP 300`状态代码，我们执行在响应正文中指定的"自定义操作". 该响应包含允许代理`push`操作在**主**节点上发生的其他数据.
## Using the Tracking Database[](#using-the-tracking-database "Permalink")
除了要复制的主数据库外，Geo **辅助**节点还具有自己的单独的[跟踪数据库](#tracking-database) .
跟踪数据库包含**辅助**节点的状态.
任何需要在升级过程中运行的数据库迁移都需要应用于每个**辅助**节点上的跟踪数据库.
### Configuration[](#configuration "Permalink")
数据库配置在[`config/database_geo.yml`](https://gitlab.com/gitlab-org/gitlab/blob/master/config/database_geo.yml.postgresql)设置. [`ee/db/geo`](https://gitlab.com/gitlab-org/gitlab/tree/master/ee/db/geo)目录包含此数据库的架构和迁移.
要为数据库编写迁移，请使用`GeoMigrationGenerator` ：
```
rails g geo_migration [args] [options]
```
要迁移跟踪数据库，请运行：
```
bundle exec rake geo:db:migrate
```
### Foreign Data Wrapper[](#foreign-data-wrapper "Permalink")
在 GitLab 10.1 中引入.
[地理日志游标](#geo-log-cursor)使用了外部数据包装器（ [FDW](#fdw) ），并提高了许多同步操作的性能.
FDW 是 PostgreSQL 扩展（ [`postgres_fdw`](https://s0www0postgresql0org.icopy.site/docs/11/postgres-fdw.html) ），已在 Geo Tracking 数据库中（在**辅助**节点上）启用，它允许它连接到只读数据库副本并执行查询和过滤来自两个实例的数据.
该持久连接被配置为名为`gitlab_secondary`的 FDW 服务器. 此配置仅存在于数据库的用户上下文中. 要访问`gitlab_secondary` ，GitLab 需要使用先前配置的同一数据库用户.
地理跟踪数据库以常规用户身份通过FDW 访问只读数据库副本，受其自身限制的限制. 凭据被配置为与先前映射的`SERVER` （ `gitlab_secondary` ）相关联的`USER MAPPING` .
FDW 配置和凭据定义由 Omnibus GitLab `gitlab-ctl reconfigure`命令自动管理.
#### Refreshing the Foreign Tables[](#refreshing-the-foreign-tables "Permalink")
每当在**主**节点上配置了新的地理节点或数据库架构更改时，都必须通过运行以下命令来刷新**辅助**节点上的外部表：
```
bundle exec rake geo:db:refresh_foreign_tables
```
否则，将阻止**辅助**节点正常运行. **辅助**节点将生成错误消息，如以下 PostgreSQL 错误所示：
```
ERROR: relation "gitlab_secondary.ci_job_artifacts" does not exist at character 323
STATEMENT: SELECT a.attname, format_type(a.atttypid, a.atttypmod),
pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod
FROM pg_attribute a LEFT JOIN pg_attrdef d
ON a.attrelid = d.adrelid AND a.attnum = d.adnum
WHERE a.attrelid = '"gitlab_secondary"."ci_job_artifacts"'::regclass
AND a.attnum > 0 AND NOT a.attisdropped
ORDER BY a.attnum
```
#### Accessing data from a Foreign Table[](#accessing-data-from-a-foreign-table "Permalink")
在 SQL 级别，您要做的就是从`gitlab_secondary.*` `SELECT`数据.
这是一个如何从地理跟踪数据库的 FDW 访问所有项目的示例：
```
SELECT * FROM gitlab_secondary.projects;
```
作为一个更真实的示例，这是在"跟踪数据库"中过滤未归档项目的方式：
```
SELECT project_registry.*
FROM project_registry
JOIN gitlab_secondary.projects
ON (project_registry.project_id = gitlab_secondary.projects.id
AND gitlab_secondary.projects.archived IS FALSE)
```
在 ActiveRecord 级别，我们还有其他表示外部表的模型. 必须以稍微不同的方式映射它们，并且它们是只读的.
检查`ee/app/models/geo/fdw`现有的 FDW 模型以供参考.
从开发人员的角度来看，这与创建代表数据库视图的模型没有什么不同.
通过上面的示例，您可以通过以下方式访问项目：
```
Geo::Fdw::Project.all
```
并通过未归档的项目访问`ProjectRegistry`过滤：
```
# We have to use Arel here:
project_registry_table = Geo::ProjectRegistry.arel_table
fdw_project_table = Geo::Fdw::Project.arel_table
project_registry_table.join(fdw_project_table)
.on(project_registry_table[:project_id].eq(fdw_project_table[:id]))
.where((fdw_project_table[:archived]).eq(true)) # if you append `.to_sql` you can check generated query
```
## Finders[](#finders "Permalink")
Geo 使用[Finders](https://gitlab.com/gitlab-org/gitlab/tree/master/app/finders) ，这是一些类，可以帮助您轻松查找项目/附件/等. 在跟踪数据库和主数据库中.
### Finders Performance[](#finders-performance "Permalink")
查找者需要将主数据库中的数据与跟踪数据库中的数据进行比较. 例如，计算已同步项目的数量通常涉及从一个数据库中检索项目 ID，并检查它们在另一个数据库中的状态. 这很慢并且需要大量内存.
为了克服这个问题，查找器使用[FDW](#fdw)或外部数据包装器. 这允许在主数据库和跟踪数据库之间进行常规的`JOIN` .
## Redis[](#redis "Permalink")
Redis 的**辅助**节点上的工作方式相同的**主**节点上. 它用于缓存，存储会话和其他持久性数据.
不使用**主**节点和**辅助**节点之间的 Redis 数据复制，因此会话等不在节点之间共享.
## Object Storage[](#object-storage "Permalink")
GitLab 可以选择使用对象存储来存储否则将存储在磁盘上的数据. 这些事情可以是：
* LFS Objects
* CI 工作工件
* Uploads
Geo 不处理存储在对象存储中的对象. Geo 会忽略对象存储中的项目. 要么：
* 对象存储层应注意其自身的地理复制.
* 所有辅助节点应使用相同的存储节点.
## Verification[](#verification "Permalink")
### Repository verification[](#repository-verification "Permalink")
存储库将通过校验和进行验证.
**主**节点在存储库上计算校验和. 它基本上将所有 Git 引用散列在一起，并将该散列存储在数据库的`project_repository_states`表中.
**次**节点执行相同操作以计算其克隆的哈希，然后将哈希与**主**节点计算出的值进行比较. 如果存在不匹配，Geo 会将其标记为不匹配，管理员可以在[Geo 管理面板中](../user/admin_area/geo_nodes.html)看到此不匹配.
## Glossary[](#glossary "Permalink")
### Primary node[](#primary-node "Permalink")
**主**节点是地理设置中具有读写功能的单个节点. 这是事实的唯一来源，Geo **次要**节点从那里复制数据.
在地理位置设置中，只能有一个**主**节点. 所有**辅助**节点都连接到该**主**节点.
### Secondary node[](#secondary-node "Permalink")
**辅助**节点是在不同地理位置运行的**主要**节点的只读副本.
### Streaming replication[](#streaming-replication "Permalink")
Geo 取决于 PostgreSQL 的流复制功能. 它完全复制数据库数据和数据库模式. 数据库副本是只读副本.
流复制取决于预写日志或 WAL. 这些日志将复制到副本并在此处重放.
由于流复制还可以复制架构，因此数据库迁移不需要在辅助节点上运行.
### Tracking database[](#tracking-database "Permalink")
每个 Geo **辅助**节点上的数据库，该数据库保留其所在节点的状态. 在[使用跟踪数据库中](#using-the-tracking-database)阅读更多[信息](#using-the-tracking-database) .
### FDW[](#fdw "Permalink")
外部数据包装程序（FDW）是 PostgreSQL 内置的功能. 它允许从不同的数据源查询数据. 在 Geo 中，它用于查询来自不同 PostgreSQL 实例的数据.
## Geo Event Log[](#geo-event-log "Permalink")
Geo **主数据库**将事件存储在`geo_event_log`表中. 日志中的每个条目都包含特定类型的事件. 这些类型的事件包括：
* 存储库已删除事件
* 存储库重命名事件
* 存储库更改事件
* 存储库创建事件
* 哈希存储迁移事件
* Lfs 对象已删除事件
* 哈希存储附件事件
* Job Artifact Deleted 事件
* 上载已删除的活动
### Geo Log Cursor[](#geo-log-cursor "Permalink")
在寻找新的`Geo::EventLog`行的**辅助**节点上运行的进程.
## Code features[](#code-features "Permalink")
### `Gitlab::Geo` utilities[](#gitlabgeo-utilities "Permalink")
与 Geo 相关的小型实用工具方法进入[`ee/lib/gitlab/geo.rb`](https://gitlab.com/gitlab-org/gitlab/blob/master/ee/lib/gitlab/geo.rb)文件.
其中许多方法都使用`RequestStore`类进行缓存，以减少在整个代码库中使用这些方法对性能的影响.
#### Current node[](#current-node "Permalink")
类方法`.current_node`返回当前节点的`GeoNode`记录.
我们使用`gitlab.yml`的`host` ， `port`和`relative_url_root`值，并在数据库中搜索以标识我们所在的节点（请参见`GeoNode.current_node` ）.
#### Primary or secondary[](#primary-or-secondary "Permalink")
要确定当前节点是**主**节点还是**辅助**节点，请使用`.primary?` 和`.secondary?` 类方法.
当未启用节点时，这些方法都可能在节点上都返回`false` . 请参阅[启用](#enablement) .
#### Geo Database configured?[](#geo-database-configured "Permalink")
处理初始化期间发生的事情时，还有一个附加的陷阱. 在一些地方，我们使用`Gitlab::Geo.geo_database_configured?` 检查节点是否具有跟踪数据库的方法，该数据库仅存在于**辅助**节点上. 这克服了在引导新节点期间可能发生的竞争条件.
#### Enablement[](#enablement "Permalink")
当用户拥有包括功能的有效许可证，并且在"地理节点"屏幕上定义了至少一个节点时，我们认为地理功能已启用.
See `Gitlab::Geo.enabled?` and `Gitlab::Geo.license_allows?` methods.
#### Read-only[](#read-only "Permalink")
所有地理**辅助**节点均为只读.
[只读数据库](verifying_database_capabilities.html#read-only-database)的一般原则适用于所有 Geo **辅助**节点. 那么`Gitlab::Database.read_only?` 方法将始终在**辅助**节点上返回`true` .
当由于节点是**辅助**节点而不允许某些写操作时，请考虑添加`Gitlab::Database.read_only?` 还是`Gitlab::Database.read_write?` 后卫，而不是`Gitlab::Geo.secondary?` .
在复制的设置中，数据库本身已经是只读的，因此我们无需为此采取任何额外的步骤.
## Steps needed to replicate a new data type[](#steps-needed-to-replicate-a-new-data-type "Permalink")
随着 GitLab 的发展，我们不断需要向 Geo 复制系统添加新资源. 具体实现取决于资源的具体情况，但是需要注意以下几点：
* 主站点上的事件生成. 每当更改/更新新资源时，我们都需要为 Log Cursor 创建一个任务.
* 事件处理. 日志游标需要为主站点生成的每种事件类型都有一个处理程序.
* 派遣工人（临时工）. 确保回填条件良好.
* 同步工作者.
* 注册所有可能的状态.
* Verification.
* 清洁器. 更改辅助站点的同步设置后，需要清理一些资源.
* 地理节点状态. 我们需要在 GitLab 管理区域中提供 API 端点以及一些演示.
* 健康检查. 如果我们可以执行一些预检查并在出现问题时使节点不正常，则应该这样做. `rake gitlab:geo:check`命令也必须更新.
### Geo self-service framework (alpha)[](#geo-self-service-framework-alpha "Permalink")
我们开始开发新的[Geo 自助服务框架（alpha）](geo/framework.html) ，这使添加新数据类型变得容易得多.
## History of communication channel[](#history-of-communication-channel "Permalink")
自从第一次迭代以来，沟通渠道已经发生了变化，您可以在此处查看历史性决策以及我们为何迁移到新实现的原因.
### Custom code (GitLab 8.6 and earlier)[](#custom-code-gitlab-86-and-earlier "Permalink")
在 8.6 之前的 GitLab 版本中，自定义代码用于处理 HTTP 请求从**主**节点到**辅助**节点的通知.
### System hooks (GitLab 8.7 to 9.5)[](#system-hooks-gitlab-87-to-95 "Permalink")
后来，决定放弃自定义代码，开始使用系统挂钩. 使用它们的人越来越多，因此许多人将从对该通信层进行的改进中受益.
我们的 API 代码（Grape）中有一个特定的**内部**端点，该端点接收来自此系统挂钩的所有请求： `/api/v4/geo/receive_events` .
我们通过`event_name`字段切换和过滤每个事件.
### Geo Log Cursor (GitLab 10.0 and up)[](#geo-log-cursor-gitlab-100-and-up "Permalink")
从 GitLab 10.0 开始，不再使用[系统 Webhooks](#system-hooks-gitlab-87-to-95) ， [而是](#system-hooks-gitlab-87-to-95)使用 Geo Log Cursor. 日志光标遍历`Geo::EventLog`行以查看自上次检查日志以来是否有更改，并将处理存储库更新，删除，更改和重命名.
该表位于复制的数据库中. 与旧方法相比，它具有两个优点：
* 复制是同步的，我们保留事件的顺序.
* 事件的复制与数据库中的更改同时发生.
## Self-service framework[](#self-service-framework "Permalink")
如果您想为正在处理的资源添加简单的地理复制，请查看我们的[自助服务框架](geo/framework.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