What problem will this feature address?
The current docs give conflicting advice: the Docker‑Compose guide tells users to use the ../files folder for persistent data, while the Volume‑Backups guide recommends Docker named volumes for automatic backups. This inconsistency confuses users and makes it unclear which method to follow.
See docs.dokploy.com/docs/core/docker-compose and docs.dokploy.com/docs/core/volume-backups
Describe the solution you'd like
Update the documentation so that both sections present a unified approach. Choose one recommended method (e.g., Docker named volumes) and explain how it satisfies both persistence and backup needs, or clearly differentiate the two use cases with explicit guidance on when to use each.
Describe alternatives you've considered
- Keep both methods but add a comparison table highlighting pros/cons.
- Create a separate “Choosing a persistence strategy” page that links to both guides.
A single, consistent recommendation (or a clear decision guide) would resolve the confusion.
Additional context
No response
What problem will this feature address?
The current docs give conflicting advice: the Docker‑Compose guide tells users to use the ../files folder for persistent data, while the Volume‑Backups guide recommends Docker named volumes for automatic backups. This inconsistency confuses users and makes it unclear which method to follow.
See docs.dokploy.com/docs/core/docker-compose and docs.dokploy.com/docs/core/volume-backups
Describe the solution you'd like
Update the documentation so that both sections present a unified approach. Choose one recommended method (e.g., Docker named volumes) and explain how it satisfies both persistence and backup needs, or clearly differentiate the two use cases with explicit guidance on when to use each.
Describe alternatives you've considered
A single, consistent recommendation (or a clear decision guide) would resolve the confusion.
Additional context
No response