per-routine rsync option? #5
Labels
No Label
?/support
accepted
bug/defect
design flaw
design note
duplicate
enhancement
fix in dev
help wanted
invalid
needs info
rejected
feedback?
upstream
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: ITwrxOrg/EZ-Bkup#5
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Right now, EZ-Bkup envokes rsync in a way where it doesn't delete files from the Destination that no longer exist in the Source. This is more safe, as some people may just want a cumalative backup, and not so much a sync of current state. EZ-Bkup could offer the "sync" behavior as a simple alternative when creating/editing routines.
EZ-Bkup must remain easy to use with as few decisions as possible (even more so with lower-level rsync decisions), but this option might be desired by enough users to be worth it.
It's also possible we could show the default behavior, as default, with short explanation, then allow users to expand an "advanced rsync options" section with more rsync options hidden away there. This strays somewhat from the original goal of a zero-config bkup util, though, and could be a slippery slope. It would be optional, which is better than "forced decisions to use", but still "dangerous" from a design/scope standpoint.
Will think about it, and maybe even wait for user feedback.