Previews should not share volumes per default
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
It feels unsafe that previews per default uses same mounts as the application. By mistake you mess with the production data.
Describe the solution you'd like
Pri 1: disable that as default.
Useful additions to that:
- configable preview volumes. isolated pr preview or shared
- option to copy live data to preview volume
Describe alternatives you've considered
Workaround is to make the app logic handle this using env as you need anyway for external services such as api keys etc. But the production environment on the dokploy server should protect the dokploy application data.
Additional context
No response
Will you send a PR to implement it?
No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Trace how preview deployments select and mount application volumes, then determine where the default can be changed without affecting regular deployments. Done means previews no longer share application mounts by default; configurable isolation, sharing, and live-data copying are listed as additional options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100