local-it/vikunja-api
0
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Fix reference to reverse proxies in docs

Browse source
This commit is contained in:
kolaente 2020-05-06 21:02:58 +02:00
parent 1fdc51078e
commit 497499e221
No known key found for this signature in database
GPG key ID: F40E70337AB24C9B
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/content/doc/setup/install-frontend.md
View file

@ -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 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`. 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 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. 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. Just open the file with a text editor - there are comments which will explain how to set the url.