-
Notifications
You must be signed in to change notification settings - Fork 0
backUp - Explore alternatives to rsync #12
Copy link
Copy link
Open
Labels
designIndicates that design/evaluation is required rather than code, unit test, or documentation work.Indicates that design/evaluation is required rather than code, unit test, or documentation work.
Description
Activity
Metadata
Metadata
Assignees
Labels
designIndicates that design/evaluation is required rather than code, unit test, or documentation work.Indicates that design/evaluation is required rather than code, unit test, or documentation work.
Projects
- StatusShow more project fieldsBacklog
Overview
Determine what alternatives to
rsyncexist and could be used in lieu ofrsyncin casersyncisn't installed on the system.Details
Determine if there is a program that is frequently installed on systems, Unix or Linux, that replicates what
rsyncdoes. If there is, and it's not too much work to support both programs, then write a story to add support tobackUpfor said program.Said program should only be used when
rsyncisn't installed on the system.Artifact(s)
TODOin thebackUpscript doc for finding an alternative torsync.rsyncalternative.backUp'sREADME.mdfile that describes thatrsyncis a prerequisite ofbackUp.backUp's script doc that describes thatrsyncis a prerequisite to use the script.Scope
This is for evaluating alternatives to
rsync, not implementing them.Blockers
It's more important that unit tests exist and are run by a pipeline than that this feature is added, as a result, that issue #2 and #3 shale be worked first.
For the same reason, GitHub status badges shale be created first (issues #4 & #5).
Understanding the level of unit test coverage for each theoretically supported shell, and increasing that coverage is of grater importance than this issue, as a result, #7, and the issues produced by it, should be worked prior to this one.