FEATURE: Extend scope of "PRUNE_BACKUPS_*", to support x amount of backups, and maybe even "x amount of space used"
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 538
- Forks
- 69
- Avg merge
- 3h 28m
- Merged PRs (30d)
- 2
Description
Hi,
I've tried to look through the docs and the code for a "max amount of backups", or "max amount of space" before backup-deletion.
Would you consider to expand the scope to include that?
(Today I filled up our server, by creating a backup every 30 minute :smile:. I guess it's overlapping a bit with restic, but I'd like to keep it simple)
Thank you for the solution, btw.
Contributor guide
No contributing guide indexed for this repository
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 reading the documentation and code that define the PRUNE_BACKUPS_* settings. Clarify whether the limit should be a backup count, a storage-space threshold, or both, then verify that backup deletion enforces the agreed limit without affecting backup creation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100