diff options
author | Marcel Amirault <ravlen@gmail.com> | 2019-03-27 07:17:02 +0300 |
---|---|---|
committer | Evan Read <eread@gitlab.com> | 2019-03-27 07:17:02 +0300 |
commit | 8b42fe3b915512344d6ebb906983a77cad7cf6e2 (patch) | |
tree | 1cea470e63105f48e03f20487df7e98cc2e584bd /doc/administration | |
parent | 5f0908bead7309354ae8d513ef85fb042ecd6b0a (diff) |
Docs: Fix more anchors, mostly pipeline related
Diffstat (limited to 'doc/administration')
-rw-r--r-- | doc/administration/repository_storage_types.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/administration/repository_storage_types.md b/doc/administration/repository_storage_types.md index 25c3d564560..4e1e363888d 100644 --- a/doc/administration/repository_storage_types.md +++ b/doc/administration/repository_storage_types.md @@ -142,7 +142,7 @@ projects: 2. Uncheck the **Use hashed storage paths for newly created and renamed projects** checkbox. To schedule a complete rollback, see the -[rake task documentation for storage rollback][rake/rollback-to-legacy] for instructions. +[rake task documentation for storage rollback](raketasks/storage.md#rollback-from-hashed-storage-to-legacy-storage) for instructions. The rollback task also supports specifying a range of Project IDs. Here is an example of limiting the rollout to Project IDs 50 to 100, in an Omnibus Gitlab installation: @@ -205,6 +205,5 @@ They are also S3 compatible since **10.0** (GitLab Premium), and available in Gi [ce-2821]: https://gitlab.com/gitlab-com/infrastructure/issues/2821 [ce-28283]: https://gitlab.com/gitlab-org/gitlab-ce/issues/28283 [rake/migrate-to-hashed]: raketasks/storage.md#migrate-existing-projects-to-hashed-storage -[rake/rollback-to-legacy]: raketasks/storage.md#rollback [storage-paths]: repository_storage_types.md [gitaly]: gitaly/index.md |