VladPolskiy/gitlab-foss
1
0
Fork 0
mirror of https://gitlab.com/gitlab-org/gitlab-foss.git synced 2025-08-15 21:39:00 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

Add latest changes from gitlab-org/gitlab@master

Browse Source
This commit is contained in:
GitLab Bot
2025-05-01 18:12:25 +00:00
parent 3901ed083c
commit bba3711c3d
41 changed files with 347 additions and 78 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/administration/operations/fast_ssh_key_lookup.md
View File

@ -101,7 +101,7 @@ To set up fast lookup with OpenSSH:
- Self-compiled installations: If you followed the instructions for
[installing GitLab Shell from source](../../install/installation.md#install-gitlab-shell), the command should be
located at `/home/git/gitlab-shell/bin/gitlab-shell-authorized-keys-check`.
Consider creating a wrapper script somewhere else, as this command must be owned by `root`,
Consider creating a wrapper script somewhere else because this command must be owned by `root`,
and not be writable by a group or others.
Also consider changing the ownership of this command as needed, but this might require temporary
ownership changes during `gitlab-shell` upgrades.
@ -126,7 +126,7 @@ To set up fast lookup with OpenSSH:
```
A successful pull or [welcome message](../../user/ssh.md#verify-that-you-can-connect)
means that GitLab found the key in the database, as the key is not present in the file.
means that GitLab found the key in the database because the key is not present in the file.
If there are lookup failures, the `authorized_keys` file is still scanned.
Git SSH performance might still be slow for many users, as long as the large file exists.
@ -172,7 +172,7 @@ GitLab supports `authorized_keys` database lookups with [SELinux](https://en.wik
Because the SELinux policy is static, GitLab doesn't support changing
internal web server ports. Administrators would have to create a special `.te`
file for the environment, as it isn't generated dynamically.
file for the environment because it isn't generated dynamically.
### Additional documentation

2
doc/administration/operations/rails_console.md
View File

@ -530,7 +530,7 @@ user.password_confirmation = 'hunter2'
user.save!(validate: false)
```
This is not recommended, as validations are usually put in place to ensure the
This is not recommended because validations are usually put in place to ensure the
integrity and consistency of user-provided data.
A validation error prevents the entire object from being saved to