Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
8b9cadff
Commit
8b9cadff
authored
Jun 15, 2021
by
Evan Read
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update navigation paths in Gitaly-related documentation for new Menu
parent
b5261c3c
Changes
6
Show whitespace changes
Inline
Side-by-side
Showing
6 changed files
with
22 additions
and
12 deletions
+22
-12
doc/administration/gitaly/index.md
doc/administration/gitaly/index.md
+2
-1
doc/administration/gitaly/praefect.md
doc/administration/gitaly/praefect.md
+7
-3
doc/administration/repository_checks.md
doc/administration/repository_checks.md
+6
-3
doc/administration/repository_storage_paths.md
doc/administration/repository_storage_paths.md
+3
-2
doc/administration/repository_storage_types.md
doc/administration/repository_storage_types.md
+2
-2
doc/user/admin_area/settings/gitaly_timeouts.md
doc/user/admin_area/settings/gitaly_timeouts.md
+2
-1
No files found.
doc/administration/gitaly/index.md
View file @
8b9cadff
...
...
@@ -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
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.
#### Use `gitaly-debug`
...
...
doc/administration/gitaly/praefect.md
View file @
8b9cadff
...
...
@@ -901,9 +901,13 @@ Particular attention should be shown to:
gitlab-rake gitlab:gitaly:check
```
1.
Check in
**Admin Area > Settings > Repository > Repository storage**
that the Praefect storage
is configured to store new repositories. Following this guide, the
`default`
storage should have
weight 100 to store all new repositories.
1.
Check that the Praefect storage is configured to store 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
"Initialize repository with a README" box so that there is content in the
...
...
doc/administration/repository_checks.md
View file @
8b9cadff
...
...
@@ -41,9 +41,12 @@ in the [`repocheck.log` file](logs.md#repochecklog) on disk:
-
`/var/log/gitlab/gitlab-rails`
for Omnibus GitLab installations
-
`/home/git/gitlab/log`
for installations from source
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**
.
If the periodic repository check causes false alarms, you can clear all repository check states by:
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
...
...
doc/administration/repository_storage_paths.md
View file @
8b9cadff
...
...
@@ -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
can choose where new repositories are stored:
1. Go to the Admin Area (**{admin}**).
1. Go to **Settings > Repository** and expand the **Repository storage** section.
1. On the top bar, select **Menu >** **{admin}** **Admin**.
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. Select **Save changes**.
...
...
doc/administration/repository_storage_types.md
View file @
8b9cadff
...
...
@@ -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:
1.
Go to the
**Admin Area**
(
**{admin}**
)
.
1.
Go to
**Overview > Projects**
and select the project.
1.
On the top bar, select
**Menu >**
**{admin}**
**Admin**
.
1.
On the left sidebar, select
**Overview > Projects**
and select the project.
The
**Gitaly relative path**
is displayed there and looks similar to:
...
...
doc/user/admin_area/settings/gitaly_timeouts.md
View file @
8b9cadff
...
...
@@ -12,7 +12,8 @@ configured to make sure that long running Gitaly calls don't needlessly take up
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.
## Available timeouts
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment