vikunja
/
vikunja
6
43
Fork 72
Code Issues 150 Pull Requests 17 Packages Releases 32 Activity

fix(docs): image urls in synology setup explanation

This commit is contained in:
kolaente 2022-06-30 16:25:24 +02:00
parent d0e09d69d0
commit ad17ff5c32
Signed by: konrad
GPG Key ID: F40E70337AB24C9B
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/content/doc/setup/full-docker-example.md
View File

@ -379,7 +379,7 @@ you can prepare 2 proxy rules:
* a redirection rule for vikunja's api (see example screenshot using port 3456) * a redirection rule for vikunja's api (see example screenshot using port 3456)
* a similar redirection rule for vikunja's frontend (using port 4321) * a similar redirection rule for vikunja's frontend (using port 4321)
![Synology Proxy Settings](/synology-proxy-1.png) ![Synology Proxy Settings](/docs/synology-proxy-1.png)
You should also add 2 empty folders for mariadb and vikunja inside Synology's You should also add 2 empty folders for mariadb and vikunja inside Synology's
docker main folders: docker main folders:
@ -399,7 +399,7 @@ To do that, you can
2. Give it the name Vikunja and paste the adapted docker compose file 2. Give it the name Vikunja and paste the adapted docker compose file
3. Deploy the Stack with the "Delpoy Stack" button: 3. Deploy the Stack with the "Delpoy Stack" button:
![Portainer Stack deploy](/synology-proxy-2.png) ![Portainer Stack deploy](/docs/synology-proxy-2.png)
The docker-compose file we're going to use is very similar to the [example without any proxy](#example-without-any-proxy) above: The docker-compose file we're going to use is very similar to the [example without any proxy](#example-without-any-proxy) above: