As far as I understood rclone, the two lines in file-tree
UPLOAD="cloud:reMarkable"
and
"${RCLONE}" sync ${VERBOSE:+--verbose} --config ${RCLONE_CONFIG} --delete-excluded "${TGTROOT}/" "${UPLOAD}/"
are in combination rather dangerous, due to the --delete-excluded, as it deletes all files on the remote folder, which are not part of the remarkable folder. If a user mis-configures the path in the first line, this could lead to large data loose.
E.g.
UPLOAD="cloud:/"
could/would potentially delete the entire cloud storage.
I notice this, when I used a already populated remarkable folder. All existing data were gone after the first call of file-tree -s
I might be wrong, but to scare to test this on / ;)
As far as I understood rclone, the two lines in file-tree
UPLOAD="cloud:reMarkable"and
"${RCLONE}" sync ${VERBOSE:+--verbose} --config ${RCLONE_CONFIG} --delete-excluded "${TGTROOT}/" "${UPLOAD}/"are in combination rather dangerous, due to the --delete-excluded, as it deletes all files on the remote folder, which are not part of the remarkable folder. If a user mis-configures the path in the first line, this could lead to large data loose.
E.g.
UPLOAD="cloud:/"could/would potentially delete the entire cloud storage.
I notice this, when I used a already populated remarkable folder. All existing data were gone after the first call of
file-tree -sI might be wrong, but to scare to test this on / ;)