Commit 8c7c7a7d authored by Nick Gaskill's avatar Nick Gaskill

Merge branch 'eread/update-gitaly-docs-for-new-menu' into 'master'

Update navigation paths in Gitaly-related documentation for new Menu

See merge request gitlab-org/gitlab!64059
parents 4741561d 8b9cadff
...@@ -398,7 +398,8 @@ See also [Gitaly timeout](../../user/admin_area/settings/gitaly_timeouts.md) set ...@@ -398,7 +398,8 @@ See also [Gitaly timeout](../../user/admin_area/settings/gitaly_timeouts.md) set
When using standalone Gitaly servers, you must make sure they are the same version When using standalone Gitaly servers, you must make sure they are the same version
as GitLab to ensure full compatibility: as GitLab to ensure full compatibility:
1. Go to **Admin Area > Overview > Gitaly Servers** on your GitLab instance. 1. On the top bar, select **Menu >** **{admin}** **Admin** on your GitLab instance.
1. On the left sidebar, select **Overview > Gitaly Servers**.
1. Confirm all Gitaly servers indicate that they are up to date. 1. Confirm all Gitaly servers indicate that they are up to date.
#### Use `gitaly-debug` #### Use `gitaly-debug`
......
...@@ -901,9 +901,13 @@ Particular attention should be shown to: ...@@ -901,9 +901,13 @@ Particular attention should be shown to:
gitlab-rake gitlab:gitaly:check gitlab-rake gitlab:gitaly:check
``` ```
1. Check in **Admin Area > Settings > Repository > Repository storage** that the Praefect storage 1. Check that the Praefect storage is configured to store new repositories:
is configured to store new repositories. Following this guide, the `default` storage should have
weight 100 to store all new repositories. 1. On the top bar, select **Menu >** **{admin}** **Admin**.
1. On the left sidebar, select **Settings > Repository**.
1. Expand the **Repository storage** section.
Following this guide, the `default` storage should have weight 100 to store all new repositories.
1. Verify everything is working by creating a new project. Check the 1. Verify everything is working by creating a new project. Check the
"Initialize repository with a README" box so that there is content in the "Initialize repository with a README" box so that there is content in the
......
...@@ -41,9 +41,12 @@ in the [`repocheck.log` file](logs.md#repochecklog) on disk: ...@@ -41,9 +41,12 @@ in the [`repocheck.log` file](logs.md#repochecklog) on disk:
- `/var/log/gitlab/gitlab-rails` for Omnibus GitLab installations - `/var/log/gitlab/gitlab-rails` for Omnibus GitLab installations
- `/home/git/gitlab/log` for installations from source - `/home/git/gitlab/log` for installations from source
If the periodic repository check causes false alarms, you can clear all repository check states by If the periodic repository check causes false alarms, you can clear all repository check states by:
going to **Admin Area > Settings > Repository**
(`/admin/application_settings/repository`) and clicking **Clear all repository checks**. 1. On the top bar, select **Menu >** **{admin}** **Admin**.
1. On the left sidebar, select **Settings > Repository** (`/admin/application_settings/repository`).
1. Expand the **Repository maintenance** section.
1. Select **Clear all repository checks**.
## Run a check manually ## Run a check manually
......
...@@ -140,8 +140,9 @@ Omnibus stores the repositories in a `repositories` subdirectory of the `git-dat ...@@ -140,8 +140,9 @@ Omnibus stores the repositories in a `repositories` subdirectory of the `git-dat
After you [configure](#configure-repository-storage-paths) multiple repository storage paths, you After you [configure](#configure-repository-storage-paths) multiple repository storage paths, you
can choose where new repositories are stored: can choose where new repositories are stored:
1. Go to the Admin Area (**{admin}**). 1. On the top bar, select **Menu >** **{admin}** **Admin**.
1. Go to **Settings > Repository** and expand the **Repository storage** section. 1. On the left sidebar, select **Settings > Repository** and expand the **Repository storage**
section.
1. Enter values in the **Storage nodes for new repositories** fields. 1. Enter values in the **Storage nodes for new repositories** fields.
1. Select **Save changes**. 1. Select **Save changes**.
......
...@@ -80,8 +80,8 @@ Administrators can look up a project's hashed path from its name or ID using: ...@@ -80,8 +80,8 @@ Administrators can look up a project's hashed path from its name or ID using:
To look up a project's hash path in the Admin Area: To look up a project's hash path in the Admin Area:
1. Go to the **Admin Area** (**{admin}**). 1. On the top bar, select **Menu >** **{admin}** **Admin**.
1. Go to **Overview > Projects** and select the project. 1. On the left sidebar, select **Overview > Projects** and select the project.
The **Gitaly relative path** is displayed there and looks similar to: The **Gitaly relative path** is displayed there and looks similar to:
......
...@@ -12,7 +12,8 @@ configured to make sure that long running Gitaly calls don't needlessly take up ...@@ -12,7 +12,8 @@ configured to make sure that long running Gitaly calls don't needlessly take up
To access Gitaly timeout settings: To access Gitaly timeout settings:
1. Go to **Admin Area > Settings > Preferences**. 1. On the top bar, select **Menu >** **{admin}** **Admin**.
1. On the left sidebar, select **Settings > Preferences**.
1. Expand the **Gitaly** section. 1. Expand the **Gitaly** section.
## Available timeouts ## Available timeouts
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment