backup-app ignores time-schedule
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 272
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
I set the plan to 3 - 5 o'clock in the morning, but the cms made the backup this afternoon (1400~, 2pm). That's a bit awful, because the maintenance mode is active during the backup and users got kicked and couldn't work during this (short) period. The cronjob is active and works without any problems.
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
No file or test is named. Start by tracing the backup app's cronjob and time-schedule handling, then reproduce a plan configured for 3–5 AM. Done means the backup runs within the configured window, preserves maintenance-mode behavior, and has a regression test for the schedule.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100