You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/administration/geo/_index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -124,7 +124,7 @@ the difference between Geo and Gitaly Cluster, see [Comparison to Geo](../gitaly
124
124
125
125
## How it works
126
126
127
-
This is a brief summary of how Geo works in your GitLab environment. For a more detailed information, see the [Geo Development page](../../development/geo.md).
127
+
This is a brief summary of how Geo works in your GitLab environment. For more details, see the Geo development documentation.
128
128
129
129
Your Geo instance can be used for cloning and fetching projects, in addition to reading any data. This makes working with large repositories over large distances much faster.
Copy file name to clipboardExpand all lines: doc/administration/geo/replication/datatypes.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -94,7 +94,7 @@ on a machine:
94
94
GitLab does not require a special file system and can work with a mounted Storage Appliance. However, there can be
95
95
performance limitations and consistency issues when using a remote file system.
96
96
97
-
Geo triggers garbage collection in Gitaly to [deduplicate forked repositories](../../../development/git_object_deduplication.md#git-object-deduplication-and-gitlab-geo) on Geo secondary sites.
97
+
Geo triggers garbage collection in Gitaly to deduplicate forked repositories on Geo secondary sites.
98
98
99
99
The Gitaly gRPC API does the communication, with three possible ways of synchronization:
100
100
@@ -203,8 +203,8 @@ successfully, you must replicate their data using some other means.
203
203
| Feature | Replicated (added in GitLab version) | Verified (added in GitLab version) | GitLab-managed object storage replication (added in GitLab version) | GitLab-managed object storage verification (added in GitLab version) | Notes |
|[Application data in PostgreSQL](../../postgresql/_index.md)|**Yes** (10.2) |**Yes** (10.2) | Not applicable | Not applicable ||
206
-
|[Project repository](../../../user/project/repository/_index.md)|**Yes** (10.2) |**Yes** (10.7) | Not applicable | Not applicable | Migrated to [self-service framework](../../../development/geo/framework.md) in 16.2. See GitLab issue [#367925](https://gitlab.com/gitlab-org/gitlab/-/issues/367925) for more details.<br /><br />Behind feature flag `geo_project_repository_replication`, enabled by default in (16.3).<br /><br /> All projects, including [archived projects](../../../user/project/working_with_projects.md#archive-a-project), are replicated. |
207
-
|[Project wiki repository](../../../user/project/wiki/_index.md)|**Yes** (10.2)<sup>2</sup> |**Yes** (10.7)<sup>2</sup> | Not applicable | Not applicable | Migrated to [self-service framework](../../../development/geo/framework.md) in 15.11. See GitLab issue [#367925](https://gitlab.com/gitlab-org/gitlab/-/issues/367925) for more details.<br /><br />Behind feature flag `geo_project_wiki_repository_replication`, enabled by default in (15.11). |
206
+
|[Project repository](../../../user/project/repository/_index.md)|**Yes** (10.2) |**Yes** (10.7) | Not applicable | Not applicable | Migrated to self-service framework in 16.2. See GitLab issue [#367925](https://gitlab.com/gitlab-org/gitlab/-/issues/367925) for more details.<br /><br />Behind feature flag `geo_project_repository_replication`, enabled by default in (16.3).<br /><br /> All projects, including [archived projects](../../../user/project/working_with_projects.md#archive-a-project), are replicated. |
207
+
|[Project wiki repository](../../../user/project/wiki/_index.md)|**Yes** (10.2)<sup>2</sup> |**Yes** (10.7)<sup>2</sup> | Not applicable | Not applicable | Migrated to self-service framework in 15.11. See GitLab issue [#367925](https://gitlab.com/gitlab-org/gitlab/-/issues/367925) for more details.<br /><br />Behind feature flag `geo_project_wiki_repository_replication`, enabled by default in (15.11). |
208
208
|[Group wiki repository](../../../user/project/wiki/group.md)|[**Yes** (13.10)](https://gitlab.com/gitlab-org/gitlab/-/issues/208147)|[**Yes** (16.3)](https://gitlab.com/gitlab-org/gitlab/-/issues/323897)| Not applicable | Not applicable | Behind feature flag `geo_group_wiki_repository_replication`, enabled by default. |
209
209
|[Uploads](../../uploads.md)|**Yes** (10.2) |**Yes** (14.6) |[**Yes** (15.1)](https://gitlab.com/groups/gitlab-org/-/epics/5551)|[**Yes** (16.4)<sup>3</sup>](https://gitlab.com/groups/gitlab-org/-/epics/8056)| Replication is behind the feature flag `geo_upload_replication`, enabled by default. Verification was behind the feature flag `geo_upload_verification`, removed in 14.8. |
210
210
|[LFS objects](../../lfs/_index.md)|**Yes** (10.2) |**Yes** (14.6) |[**Yes** (15.1)](https://gitlab.com/groups/gitlab-org/-/epics/5551)|[**Yes** (16.4)<sup>3</sup>](https://gitlab.com/groups/gitlab-org/-/epics/8056)| GitLab versions 11.11.x and 12.0.x are affected by [a bug that prevents any new LFS objects from replicating](https://gitlab.com/gitlab-org/gitlab/-/issues/32696).<br /><br />Replication is behind the feature flag `geo_lfs_object_replication`, enabled by default. Verification was behind the feature flag `geo_lfs_object_verification`, removed in 14.7. |
@@ -232,6 +232,6 @@ successfully, you must replicate their data using some other means.
232
232
233
233
**Footnotes:**
234
234
235
-
1. Migrated to [self-service framework](../../../development/geo/framework.md) in 15.5. See GitLab issue [#337436](https://gitlab.com/gitlab-org/gitlab/-/issues/337436) for more details.
236
-
1. Migrated to [self-service framework](../../../development/geo/framework.md) in 15.11. Behind feature flag `geo_project_wiki_repository_replication`, enabled by default. See GitLab issue [#367925](https://gitlab.com/gitlab-org/gitlab/-/issues/367925) for more details.
235
+
1. Migrated to self-service framework in 15.5. See GitLab issue [#337436](https://gitlab.com/gitlab-org/gitlab/-/issues/337436) for more details.
236
+
1. Migrated to self-service framework in 15.11. Behind feature flag `geo_project_wiki_repository_replication`, enabled by default. See GitLab issue [#367925](https://gitlab.com/gitlab-org/gitlab/-/issues/367925) for more details.
237
237
1. Verification of files stored in object storage was [introduced](https://gitlab.com/groups/gitlab-org/-/epics/8056) in GitLab 16.4 [with a feature flag](../../feature_flags.md) named `geo_object_storage_verification`, enabled by default.
- Learn more about GitLab [bundled software metrics](monitoring/prometheus/_index.md#bundled-software-metrics).
107
107
- Prometheus and its exporters are on by default. However, you need to [configure the service](monitoring/prometheus/_index.md#configuring-prometheus).
108
-
- Learn more about [GitLab architecture](../development/architecture.md).
109
108
- Find out why [application performance metrics](https://about.gitlab.com/blog/2020/05/07/working-with-performance-metrics/) matter.
110
109
- Integrate Grafana to [build visual dashboards](https://youtu.be/f4R7s0An1qE) based on performance metrics.
Copy file name to clipboardExpand all lines: doc/administration/maintenance_mode/_index.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -113,7 +113,7 @@ For most JSON requests, `POST`, `PUT`, `PATCH`, and `DELETE` are blocked, and th
113
113
|`POST`|`/admin/session`, `/admin/session/destroy`| To allow [Admin Mode for GitLab administrators](https://gitlab.com/groups/gitlab-org/-/epics/2158)|
114
114
|`POST`| Paths ending with `/compare`| Git revision routes. |
115
115
|`POST`|`.git/git-upload-pack`| To allow Git pull/clone. |
116
-
|`POST`|`/api/v4/internal`|[internal API routes](../../development/internal_api/_index.md)|
116
+
|`POST`|`/api/v4/internal`| internal API routes |
117
117
|`POST`|`/admin/sidekiq`| To allow management of background jobs in the **Admin** area |
118
118
|`POST`|`/admin/geo`| To allow updating Geo Nodes in the administrator UI |
119
119
|`POST`|`/api/v4/geo_replication`| To allow certain Geo-specific administrator UI actions on secondary sites |
@@ -190,7 +190,7 @@ To monitor queues and disable jobs:
190
190
191
191
### Feature flags
192
192
193
-
-[Development feature flags](../../development/feature_flags/_index.md) cannot be turned on or off through the API, but can be toggled through the Rails console.
193
+
- Development feature flags cannot be turned on or off through the API, but can be toggled through the Rails console.
194
194
-[The feature flag service](../../operations/feature_flags.md) responds to feature flag checks but feature flags cannot be toggled
Copy file name to clipboardExpand all lines: doc/administration/silent_mode/_index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -126,6 +126,6 @@ Outbound communications from the following features are not silenced by Silent M
126
126
|[File hooks](../file_hooks.md)||
127
127
|[Server hooks](../server_hooks.md)||
128
128
|[Advanced search](../../integration/advanced_search/elasticsearch.md)| If two GitLab instances are using the same Advanced Search instance, then they can both modify Search data. This is a split-brain scenario which can occur for example after promoting a secondary Geo site while the primary Geo site is live. |
129
-
|[Snowplow](../../development/internal_analytics/product_analytics.md)| There is [a proposal to silence these requests](https://gitlab.com/gitlab-org/gitlab/-/issues/409661). |
129
+
| Snowplow | There is [a proposal to silence these requests](https://gitlab.com/gitlab-org/gitlab/-/issues/409661). |
130
130
|[Deprecated Kubernetes Connections](../../user/clusters/agent/_index.md)| There is [a proposal to silence these requests](https://gitlab.com/gitlab-org/gitlab/-/issues/396470). |
131
131
|[Container registry webhooks](../packages/container_registry.md#configure-container-registry-notifications)| There is [a proposal to silence these requests](https://gitlab.com/gitlab-org/gitlab/-/issues/409682). |
Copy file name to clipboardExpand all lines: doc/ci/components/_index.md
+7-1
Original file line number
Diff line number
Diff line change
@@ -144,6 +144,12 @@ For example:
144
144
145
145
## Use a component
146
146
147
+
Prerequisites:
148
+
149
+
If you are a member of a parent group that contains the current group or project:
150
+
151
+
- You must have the minimum role set by the visibility level of the project's parent group. For example, you must have at least the Reporter role if a parent project is set to **Private**.
152
+
147
153
To add a component to a project's CI/CD configuration, use the [`include: component`](../yaml/_index.md#includecomponent)
148
154
keyword. The component reference is formatted as `<fully-qualified-domain-name>/<project-path>/<component-name>@<specific-version>`,
149
155
for example:
@@ -612,7 +618,7 @@ in your project, you can select **CI/CD Catalog**.
612
618
Visibility of components in the CI/CD catalog follows the component source project's
613
619
[visibility setting](../../user/public_access.md). Components with source projects set to:
614
620
615
-
- Private are visible only to users assigned at least the Guest role for the source component project.
621
+
- Private are visible only to users assigned at least the Guest role for the source component project. To use a component, you must have at least the Reporter role.
616
622
- Internal are visible only to users logged into the GitLab instance.
617
623
- Public are visible to anyone with access to the GitLab instance.
Copy file name to clipboardExpand all lines: doc/cloud_seed/_index.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
stage: none
3
3
group: unassigned
4
-
info: This is a GitLab Incubation Engineering program. No technical writer assigned to this group.
4
+
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
5
5
title: Cloud Seed
6
6
---
7
7
@@ -20,7 +20,7 @@ title: Cloud Seed
20
20
{{< /history >}}
21
21
22
22
Cloud Seed is an open-source program led
23
-
by [GitLab Incubation Engineering](https://handbook.gitlab.com/handbook/engineering/development/incubation/) in collaboration with
23
+
by GitLab in collaboration with
24
24
[Google Cloud](https://cloud.google.com/).
25
25
26
26
Cloud Seed combines Heroku-like ease-of-use with hyper-cloud flexibility. We do this by using OAuth 2 to provision
@@ -170,7 +170,7 @@ There are several ways you can contribute to Cloud Seed:
170
170
171
171
- Use Cloud Seed and [share feedback](https://gitlab.com/gitlab-org/incubation-engineering/five-minute-production/feedback/-/issues/new?template=general_feedback).
172
172
- If you are familiar with Ruby on Rails or Vue.js,
173
-
consider [contributing to GitLab](../development/contributing/_index.md) as a developer.
173
+
consider contributing to GitLab as a developer.
174
174
- Much of Cloud Seed is an internal module in the GitLab codebase.
175
175
- If you are familiar with GitLab pipelines, consider contributing to
176
176
the [Cloud Seed Library](https://gitlab.com/gitlab-org/incubation-engineering/five-minute-production/library) project.
Copy file name to clipboardExpand all lines: doc/solutions/integrations/aws_googlecloud_ollama.md
-1
Original file line number
Diff line number
Diff line change
@@ -156,7 +156,6 @@ Key Highlights:
156
156
157
157
Designed for simplicity and performance, Ollama empowers users to harness the power of LLMs without the complexity of traditional AI infrastructure. Further details on setup and supported models will be covered later in the documentation.
0 commit comments