summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAnton Smith <asmith@gitlab.com>2019-08-05 22:51:29 +0000
committerAnton Smith <asmith@gitlab.com>2019-08-05 22:51:29 +0000
commite949dbacaf980ed53fde0c315aee4c4ef094444a (patch)
tree8b4fb763460ebf15a41f057c87d74b1318ec8956
parent5acbd0e087a426426adc061362bb58cc4c259e15 (diff)
downloadgitlab-ce-65606-docs-clarify-usage-of-elasticsearch-with-gitaly-nfs.tar.gz
Apply suggestion to doc/administration/gitaly/index.md65606-docs-clarify-usage-of-elasticsearch-with-gitaly-nfs
-rw-r--r--doc/administration/gitaly/index.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/administration/gitaly/index.md b/doc/administration/gitaly/index.md
index 3b45a154376..19801e3b5ea 100644
--- a/doc/administration/gitaly/index.md
+++ b/doc/administration/gitaly/index.md
@@ -45,7 +45,7 @@ be mounted on the Gitaly server.
Starting with GitLab 11.8, it is possible to use ElasticSearch in conjunction with
a Gitaly setup that isn't utilising NFS. In order to use ElasticSearch in this
-scenario, the [new repository indexer](https://docs.gitlab.com/ee/integration/elasticsearch.html#elasticsearch-repository-indexer-beta)
+scenario, the [new repository indexer](../../integration/elasticsearch.md#elasticsearch-repository-indexer-beta)
needs to be enabled in your GitLab configuration.
NOTE: **Note:** While Gitaly can be used as a replacement for NFS, it's not recommended