Commit 9a4f9b03 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Fix Vale errors

parent 8d3246cf
...@@ -930,7 +930,8 @@ are supported and can be added if needed. ...@@ -930,7 +930,8 @@ are supported and can be added if needed.
## Configure Sentinel Cache ## Configure Sentinel Cache
NOTE: **Note:** If you are using an external Redis Sentinel instance, be sure NOTE: **Note:**
If you are using an external Redis Sentinel instance, be sure
to exclude the `requirepass` parameter from the Sentinel to exclude the `requirepass` parameter from the Sentinel
configuration. This parameter will cause clients to report `NOAUTH configuration. This parameter will cause clients to report `NOAUTH
Authentication required.`. [Redis Sentinel 3.2.x does not support Authentication required.`. [Redis Sentinel 3.2.x does not support
...@@ -1055,8 +1056,6 @@ To configure the Sentinel: ...@@ -1055,8 +1056,6 @@ To configure the Sentinel:
</a> </a>
</div> </div>
## Configure Sentinel Queues ## Configure Sentinel Queues
- `10.6.0.81`: Sentinel - Queues 1 - `10.6.0.81`: Sentinel - Queues 1
...@@ -1098,7 +1097,8 @@ TIP: **Tip:** ...@@ -1098,7 +1097,8 @@ TIP: **Tip:**
For more information about Gitaly's history and network architecture see the For more information about Gitaly's history and network architecture see the
[standalone Gitaly documentation](../gitaly/index.md). [standalone Gitaly documentation](../gitaly/index.md).
Note: **Note:** The token referred to throughout the Gitaly documentation is Note: **Note:**
The token referred to throughout the Gitaly documentation is
just an arbitrary password selected by the administrator. It is unrelated to just an arbitrary password selected by the administrator. It is unrelated to
tokens created for the GitLab API or other similar web API tokens. tokens created for the GitLab API or other similar web API tokens.
...@@ -1216,7 +1216,7 @@ nodes (including the Gitaly node using the certificate) and on all client nodes ...@@ -1216,7 +1216,7 @@ nodes (including the Gitaly node using the certificate) and on all client nodes
that communicate with it following the procedure described in that communicate with it following the procedure described in
[GitLab custom certificate configuration](https://docs.gitlab.com/omnibus/settings/ssl.html#install-custom-public-certificates). [GitLab custom certificate configuration](https://docs.gitlab.com/omnibus/settings/ssl.html#install-custom-public-certificates).
NOTE: **Note** NOTE: **Note:**
The self-signed certificate must specify the address you use to access the The self-signed certificate must specify the address you use to access the
Gitaly server. If you are addressing the Gitaly server by a hostname, you can Gitaly server. If you are addressing the Gitaly server by a hostname, you can
either use the Common Name field for this, or add it as a Subject Alternative either use the Common Name field for this, or add it as a Subject Alternative
...@@ -1527,7 +1527,8 @@ On each node perform the following: ...@@ -1527,7 +1527,8 @@ On each node perform the following:
sudo gitlab-ctl tail gitaly sudo gitlab-ctl tail gitaly
``` ```
NOTE: **Note:** When you specify `https` in the `external_url`, as in the example NOTE: **Note:**
When you specify `https` in the `external_url`, as in the example
above, GitLab assumes you have SSL certificates in `/etc/gitlab/ssl/`. If above, GitLab assumes you have SSL certificates in `/etc/gitlab/ssl/`. If
certificates are not present, NGINX will fail to start. See the certificates are not present, NGINX will fail to start. See the
[NGINX documentation](https://docs.gitlab.com/omnibus/settings/nginx.html#enable-https) [NGINX documentation](https://docs.gitlab.com/omnibus/settings/nginx.html#enable-https)
......
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