itzg/docker-mc-backup

FEATURE: Extend scope of "PRUNE_BACKUPS_*", to support x amount of backups, and maybe even "x amount of space used"

Open

#98 opened on Aug 5, 2022

View on GitHub
 (7 comments) (3 reactions) (0 assignees)Shell (66 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (501 stars)
PR merge metrics
 (Avg merge 6h 9m) (8 merged PRs in 30d)

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

Research direction
Analyze the current PRUNE BACKUPS * implementation and design a solution to support maximum backup count and/or maximum storage usage. Consider environment variables for configuration and ensure backward compatibility.
Tech stack
shelldocker
Domain
devopsinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
DockerShell scripting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60