Choose what to include/exclude for cluster backup
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?
Exclude folders that should not be in the backup.
We have currently all our app volumes as /etc/dokploy/volumes (shared storage setup) and now the cluster backups are gigantic.
It would be great to add an include and exclude path so the backup can be more specific.
Describe the solution you'd like
Exclude folders that should not be in the backup.
We have currently all our app volumes as /etc/dokploy/volumes (shared storage setup) and now the cluster backups are gigantic.
It would be great to add an include and exclude path so the backup can be more specific.
Describe alternatives you've considered
N/A
Additional context
No response
Will you send a PR to implement it?
Maybe, need help
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
Start by locating the cluster-backup implementation and how application volumes such as /etc/dokploy/volumes are selected. Trace the current backup path handling before deciding where include and exclude paths belong. Done means users can specify paths and backups omit excluded folders while retaining included content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100