Commit 8eda374c authored by Collen's avatar Collen Committed by Collen Kriel

Fix relative link to point to custom hook doc

parent 62e78c1b
...@@ -328,7 +328,7 @@ When you tail the Gitaly logs on your Gitaly server you should see requests ...@@ -328,7 +328,7 @@ When you tail the Gitaly logs on your Gitaly server you should see requests
coming in. One sure way to trigger a Gitaly request is to clone a repository coming in. One sure way to trigger a Gitaly request is to clone a repository
from your GitLab server over HTTP. from your GitLab server over HTTP.
DANGER: **Danger:** If you have [custom server-side Git hooks](../blob/master/doc/administration/custom_hooks.md#custom-server-side-git-hooks) configured, either per repository or globally, you must move these to the Gitaly node. If you have multiple Gitaly nodes, copy your custom hook(s) to all nodes. DANGER: **Danger:** If you have [custom server-side Git hooks](../custom_hooks.md#custom-server-side-git-hooks) configured, either per repository or globally, you must move these to the Gitaly node. If you have multiple Gitaly nodes, copy your custom hook(s) to all nodes.
### Disabling the Gitaly service in a cluster environment ### Disabling the Gitaly service in a cluster environment
......
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