Add support for backup frequency
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
I imagine this can be used to run backups less frequently than daily, without having to change the cron job itself, which might as well run day and backup other sections.
Each section would back their own value for backup_frequency, with a default of 1 day.
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
No file or test is named. Start by locating the backup scheduling entry point and the section configuration handling, then trace how the current daily frequency is applied. Done means each section can specify backup_frequency, defaults to one day, and existing backup behavior remains unchanged when it is not set.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100