From 497499e221591745de15097b5cbe454d467757e2 Mon Sep 17 00:00:00 2001 From: kolaente Date: Wed, 6 May 2020 21:02:58 +0200 Subject: [PATCH] Fix reference to reverse proxies in docs --- docs/content/doc/setup/install-frontend.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/doc/setup/install-frontend.md b/docs/content/doc/setup/install-frontend.md index 7c43690264..bc12c9cf6d 100644 --- a/docs/content/doc/setup/install-frontend.md +++ b/docs/content/doc/setup/install-frontend.md @@ -23,7 +23,7 @@ By default, the frontend assumes it can reach the api at `/api/v1` relative to t This means that if you make the frontend available at, say `https://vikunja.example.com`, it tries to reach the api at `https://vikunja.example.com/api/v1`. In this scenario it is not possible for the frontend and the api to live on seperate servers or even just seperate -ports on the same server with [the use of a reverse proxy]({{< ref "reverse-proxy.md">}}). +ports on the same server with [the use of a reverse proxy]({{< ref "reverse-proxies.md">}}). To make configurations like this possible, the api url can be set in the `index.html` file of the frontend releases. Just open the file with a text editor - there are comments which will explain how to set the url.