Commit 58b8fb91 authored by Marcin Sedlak-Jakubowski's avatar Marcin Sedlak-Jakubowski

Merge branch 'doc-fix-vale-errors-in-encrypted-communication' into 'master'

Documentation: Fix Vale issues for ./administration/encrypted_configuration.md

See merge request gitlab-org/gitlab!60272
parents 24fdf888 b5fe0864
...@@ -18,7 +18,7 @@ In order to enable the encrypted configuration settings, a new base key needs to ...@@ -18,7 +18,7 @@ In order to enable the encrypted configuration settings, a new base key needs to
**Omnibus Installation** **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. `/etc/gitlab/gitlab-secrets.json` contains the same values on all nodes.
**GitLab Cloud Native Helm Chart** **GitLab Cloud Native Helm Chart**
...@@ -34,4 +34,4 @@ The new secret can be generated by running: ...@@ -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 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 `<path-to-gitlab-rails>/config/secrets.yml` This prints general information on the GitLab instance, but also causes the key to be generated in `<path-to-gitlab-rails>/config/secrets.yml`
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