Merge branch 'docs-update-redirects-omnibus' into 'master'

Update links to redirected files

See merge request gitlab-org/omnibus-gitlab!4666

doc/README.md

@@ -57,11 +57,11 @@ to work best with the available resources. Check out the [documentation](setting
 - [Redis](settings/redis.md)
 - [Logs](settings/logs.md)
 - [Database](settings/database.md)
-- [Reply by email](https://docs.gitlab.com/ee/incoming_email/README.html)
+- [Reply by email](https://docs.gitlab.com/ee/administration/reply_by_email.html)
 - [Environment variables](settings/environment-variables.md)
 - [`gitlab.yml`](settings/gitlab.yml.md)
 - [Backups](settings/backups.md)
-- [Pages](https://docs.gitlab.com/ee/pages/administration.html)
+- [Pages](https://docs.gitlab.com/ee/administration/pages/index.html)
 - [SSL](settings/ssl.md)
 - [GitLab and Registry](architecture/registry/README.md)
 - [Configuring an asset proxy server](https://docs.gitlab.com/ee/security/asset_proxy.html)

doc/build.md

 ---
-stage: Enablement
-group: Distribution
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
+redirect_to: 'build/README.md'
 ---
-This document has been [moved to build/README.md](build/README.md).
+This document was moved to [another location](build/README.md)

doc/development.md

-This document was moved to [development/README.md.](development/README.md)
+---
+redirect_to: 'development/README.md'
+---
+
+This document was moved to [another location](development/README.md)

doc/roles/README.md

@@ -54,7 +54,7 @@ a `gitlab-ee` Omnibus package. It will be mentioned next to each role.
 ### Redis Server Roles
-Documentation on the use of the Redis Roles can be found in [Configuring Redis Cluster](https://docs.gitlab.com/ee/administration/high_availability/redis.html#configuring-redis-ha)
+Documentation on the use of the Redis Roles can be found in [Configuring Redis for Scaling](https://docs.gitlab.com/ee/administration/redis/index.html)
 - **redis_sentinel_role** (`gitlab-ee`)
@@ -77,7 +77,7 @@ Documentation on the use of the Redis Roles can be found in [Configuring Redis C
 ### GitLab Geo Roles
 The GitLab Geo roles are used when setting up the database replication for GitLab
-Geo. See the [Geo Database Documentation](https://docs.gitlab.com/ee/gitlab-geo/database.html)
+Geo. See the [Geo Database Documentation](https://docs.gitlab.com/ee/administration/geo/setup/database.html)
 for configuration steps.
 - **geo_primary_role** (`gitlab-ee`)
@@ -95,7 +95,7 @@ for configuration steps.
 ### Monitoring Roles
-Monitoring roles are used to setup monitoring of HA installs. Additional documentation is available in the HA [Monitoring documentation](https://docs.gitlab.com/ee/administration/high_availability/monitoring_node.html).
+Monitoring roles are used to set up monitoring of installations. For additional information, see the [Monitoring documentation](https://docs.gitlab.com/ee/administration/monitoring/prometheus/index.html).
 - **monitoring_role** (`gitlab-ce`/`gitlab-ee`)
@@ -105,7 +105,7 @@ Monitoring roles are used to setup monitoring of HA installs. Additional documen
 ### PostgreSQL Roles
-Documentation on the usage of the PostgreSQL Roles can be found in [Configuring PostgreSQL multi-node](https://docs.gitlab.com/ee/administration/high_availability/database.html#configure-using-omnibus-for-high-availability)
+Documentation on the usage of the PostgreSQL Roles can be found in [Configuring PostgreSQL for Scaling](https://docs.gitlab.com/ee/administration/postgresql/index.html)
 - **postgres_role** (`gitlab-ce`/`gitlab-ee`)

doc/settings/README.md

@@ -16,7 +16,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 - [LDAP](ldap.md)
 - [Logs](logs.md)
 - [NGINX](nginx.md)
-- [Pages](https://docs.gitlab.com/ee/pages/administration.html)
+- [Pages](https://docs.gitlab.com/ee/administration/pages/index.html)
 - [Prometheus Monitoring](prometheus.md)
 - [Puma](puma.md)
 - [Raspberry Pi](rpi.md)

doc/settings/pages.md

-Documentation moved to <https://docs.gitlab.com/ee/pages/administration.html>.
+---
+redirect_to: 'https://docs.gitlab.com/ee/administration/pages/index.html'
+---
+
+This document was moved to [another location](https://docs.gitlab.com/ee/administration/pages/index.html)

doc/settings/puma.md

@@ -14,7 +14,7 @@ disabled by default.
 1. Determine suitable Puma worker and thread settings. For details, see [Puma settings](https://docs.gitlab.com/ee/install/requirements.html#puma-settings).
 1. Convert custom Unicorn settings to the equivalent Puma settings (if applicable). For details, see [Converting Unicorn settings to Puma](#converting-unicorn-settings-to-puma).
-1. For multi-node deployments, configure the load balancer to use the [readiness check](https://docs.gitlab.com/ee/administration/high_availability/load_balancer.html#readiness-check).
+1. For multi-node deployments, configure the load balancer to use the [readiness check](https://docs.gitlab.com/ee/administration/load_balancer.html#readiness-check).
 1. Reconfigure GitLab so the above changes take effect.
    ```shell

doc/update/README.md

@@ -619,7 +619,7 @@ setting `gitlab_rails['auto_migrate'] = false` in
 #### Use Redis HA (using Sentinel) **(PREMIUM ONLY)**
 Package upgrades may involve version updates to the bundled Redis service. On
-instances using [Redis HA](https://docs.gitlab.com/ee/administration/high_availability/redis.html),
+instances using [Redis for scaling](https://docs.gitlab.com/ee/administration/redis/index.html),
 upgrades must follow a proper order to ensure minimum downtime, as specified
 below. This doc assumes the official guides are being followed to setup Redis
 HA.

doc/update/gitlab_11_changes.md

@@ -111,7 +111,7 @@ Rack Attack is disabled by default. To continue using Rack Attack, you must [ena
 ### 11.6
 1. [Sidekiq probe of GitLab Monitor](https://docs.gitlab.com/ee/administration/monitoring/prometheus/gitlab_exporter.html)
-   will be disabled by default if GitLab is configured in [Redis HA mode](https://docs.gitlab.com/ee/administration/high_availability/redis.html).
+   will be disabled by default if GitLab is configured in [Redis for scaling](https://docs.gitlab.com/ee/administration/redis/index.html).
    To manually enable it, users can set `gitlab_monitor['probe_sidekiq'] = true`
    in `/etc/gitlab/gitlab.rb` file. However, when manually enabling it in Redis
    HA mode, users are expected to point the probe to a Redis instance connected