Retention Policy for Cloud Backups
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by reading the Cloud Backup implementation and the snapshot retention setting described in the issue; the payload does not name specific files or tests. Trace how snapshots are selected and uploaded, then identify where a configurable limit could apply. Done means the Cloud Backup tab can select a retention policy, such as latest only or the last five snapshots, and uploads follow that choice.
Written by the indexing model from the issue text.
Description
Problem:
I noticed that Cloud Backups will upload all the Snapshots, so that if the snapshot is limited to 20 version (default) it'll also upload the snapshots to the Cloud Backups Provider, this can lead to massive usage on the Cloud Backups.
for example I have Bloodborne setup:
the files on a single snapshot are about 1.4 MB but on my self-hosted FileBrowser Quantum using WebDAV, the game files (snapshots) are using about 39.7 MB as shown in the image below:
Suggestion:
Add a setting in Cloud Backup tab to choose Retention Policy, maybe only keep latest or keep last 5 snapshots this can help so much.
Environment:
OS: Windows 11 Pro
OpenSave Version: v2.4.1
- Dominant language
- Go
- Stars
- 225
- Forks
- 9
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 72
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from Liquid-co/OpenSave
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
All issues in Liquid-co/OpenSave
Similar issues
-
[Bug] Custom tool truncation leaves unused stream copies openPossibly taken @OUAO-FRANK claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
[v3] KeyBindingManager calls (Add/Remove) are not converted into a case-insensitive accelerator.KeyOpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
crmne/hyprmoncfg#114 · 1 comment ·
Maintainers usually reply within 1 day
-
runtime: usleep sleeps nanoseconds instead of microseconds on linux/mips and linux/mips64Possibly taken @BRobertson7 claimed this today. Opencompiler/runtime
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100