jbwittner/gitops
1
0
Fork 0
Code Issues 1 Pull requests Activity
No description
42 commits 1 branch 0 tags 473 KiB
  • Shell 100%
Find a file
Exact
renovate-bot 3d31451eb9 Update renovate/renovate Docker tag to v43.216.2 (#92)
2026-06-09 02:03:22 +00:00
dokploy Update renovate/renovate Docker tag to v43.216.2 (#92) 2026-06-09 02:03:22 +00:00
.gitignore Initial commit 2026-05-25 22:41:13 +02:00
README.md Initial commit 2026-05-25 22:41:13 +02:00
renovate.json Initial commit 2026-05-25 22:41:13 +02:00

README.md

gitops

name: Dokploy files mount path description: How to bind-mount files managed by Dokploy's Files/Mounts UI from inside a compose.yaml type: project originSessionId: 551b9a72-a993-44f8-87c8-49fb807fa1e0

In this gitops repo, compose files live at dokploy/<category>/<stack>/compose.yaml and Dokploy stores files uploaded via the "Files/Mounts" UI in a files/ directory at a higher level. To bind-mount such a file from a compose.yaml, use ../../../../files/<filename> (four levels up).

Why: Dokploy resolves bind-mount relative paths from a deeper working directory than the compose.yaml location, so a naive ../files/... path doesn't resolve to the right place. Confirmed by the user on 2026-05-08 while wiring cloudflare.ini into the postfix stack.

How to apply: When adding a Dokploy-managed secret/config file as a bind-mount in any dokploy/*/*/compose.yaml, default to ../../../../files/<name> rather than ../files/<name> or absolute paths. Do not invent volume-name workarounds — bind-mount is the Dokploy-native way.