vikunja/website
2
0
Fork 3
Code Issues 1 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

fix: add synology images
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source
This commit is contained in:
kolaente 2024-07-14 22:42:50 +02:00
parent 89a54c55e5
commit 55a1657dad
Signed by: konrad
GPG Key ID: F40E70337AB24C9B
3 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
src/assets/images/docs/synology-proxy-1.png (Stored with Git LFS) Normal file
View File

Binary file not shown.

BIN
src/assets/images/docs/synology-proxy-2.png (Stored with Git LFS) Normal file
View File

Binary file not shown.

4
src/content/docs/setup/full-docker-example.mdoc
View File

@ -288,7 +288,7 @@ services:
There is a proxy preinstalled in DSM, so if you want to access Vikunja from outside,
you need to prepare a proxy rule the Vikunja Service.
![Synology Proxy Settings](/docs/synology-proxy-1.png)
![Synology Proxy Settings](../../../assets/images/docs/synology-proxy-1.png)
You should also add 2 empty folders for MariaDB and Vikunja inside Synology's
docker main folders:
@ -308,7 +308,7 @@ To do that, you can
2. Give it the name Vikunja and paste the adapted docker compose file
3. Deploy the Stack with the "Deploy Stack" button:
![Portainer Stack deploy](/docs/synology-proxy-2.png)
![Portainer Stack deploy](../../../assets/images/docs/synology-proxy-2.png)
The docker-compose file we're going to use is exactly the same from the [example without any proxy](#example-without-any-proxy) above.