summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKatrin Leinweber <724395-katrinleinweber@users.noreply.gitlab.com>2019-04-13 15:31:45 +0000
committerKatrin Leinweber <724395-katrinleinweber@users.noreply.gitlab.com>2019-04-13 15:31:45 +0000
commitddfd99b28885abaebfc3a2bb98886dab7f3a9708 (patch)
treedaba5723f285a625207794f5bf921481f70b8ac7
parent0a99e0220d9371423039f05f700af3675b26624f (diff)
downloadgitlab-ce-ddfd99b28885abaebfc3a2bb98886dab7f3a9708.tar.gz
Complete "Repository storage" directions
-rw-r--r--doc/administration/repository_storage_types.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/administration/repository_storage_types.md b/doc/administration/repository_storage_types.md
index 4e1e363888d..88bf55296b2 100644
--- a/doc/administration/repository_storage_types.md
+++ b/doc/administration/repository_storage_types.md
@@ -110,7 +110,7 @@ enabled for all new projects.
To start a migration, enable Hashed Storage for new projects:
-1. Go to **Admin > Settings** and expand the **Repository Storage** section.
+1. Go to **Admin > Settings > Repository** and expand the **Repository Storage** section.
2. Select the **Use hashed storage paths for newly created and renamed projects** checkbox.
Check if the change breaks any existing integration you may have that
@@ -138,7 +138,7 @@ source-based installation.
Similar to the migration, to disable Hashed Storage for new
projects:
-1. Go to **Admin > Settings** and expand the **Repository Storage** section.
+1. Go to **Admin > Settings > Repository** and expand the **Repository Storage** section.
2. Uncheck the **Use hashed storage paths for newly created and renamed projects** checkbox.
To schedule a complete rollback, see the