From b5fe086493affca163fc6bcf9378eb619646d079 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Benedikt=20Br=C3=BCckmann?= <64bit+git@posteo.de> Date: Mon, 26 Apr 2021 14:07:18 +0200 Subject: [PATCH] Fix Vale issues for ./administration/encrypted_configuration.md --- doc/administration/encrypted_configuration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/administration/encrypted_configuration.md b/doc/administration/encrypted_configuration.md index 508f4314694ff8..ff48005e427ec8 100644 --- a/doc/administration/encrypted_configuration.md +++ b/doc/administration/encrypted_configuration.md @@ -18,7 +18,7 @@ In order to enable the encrypted configuration settings, a new base key needs to **Omnibus Installation** -Starting with 13.7 the new secret is automatically generated for you, but you will need to ensure your +Starting with 13.7 the new secret is automatically generated for you, but you need to ensure your `/etc/gitlab/gitlab-secrets.json` contains the same values on all nodes. **GitLab Cloud Native Helm Chart** @@ -34,4 +34,4 @@ The new secret can be generated by running: bundle exec rake gitlab:env:info RAILS_ENV=production GITLAB_GENERATE_ENCRYPTED_SETTINGS_KEY_BASE=true ``` -This will print general information on the GitLab instance, but will also cause the key to be generated in `/config/secrets.yml` +This prints general information on the GitLab instance, but also causes the key to be generated in `/config/secrets.yml` -- GitLab