In the optic of integrating this module into the Aegir 7.x-3.x distribution (see:#2180053: Include more "golden" contrib), I believe we need to significantly simplify the UI. Something along these lines of:

Backup schedule

CommentFileSizeAuthor
backup_schedule.jpg53.58 KBergonlogic

Comments

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented

FYI, I also ran the latest 6.x-2.x code through coder_upgrade, and started a 7.x-3.x branch and snapshot release, so we can assign issues to the right branch.

Evidently, implementing this would involve merging the backup queue and garbage collection modules. Is there a common use-case for running these singly?

colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
commented
Status: Active » Fixed

This appears to be done. Although I'm still not sure why there are 3 modules instead of 1. Given that there's not much value to be gained by doing this now, I think we should leave as-is, and then combine when we do this for Aegir 5.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
commented
Status: Closed (fixed) » Active

I disagree with the jerk in #2, so reopening. This is causing some serious confusion on a client installation.