Refuse a relative path on an rclone remote of type local (closes #465)
check / check (push) Waiting to run
check / check (push) Waiting to run
rclone resolves a relative path on its local backend against the working directory, so rclone://localfs/srv/backup wrote under whatever directory vaultik ran from. Opening such a destination now fails with an error that shows the absolute form, rclone://localfs//srv/backup. Other remotes keep relative paths, which rclone resolves on the remote. The README says how to write an absolute rclone path. Model: opus-5-5
This commit was merged in pull request #475.
This commit is contained in:
1 parent
d747ddef3a
commit
9fedcbeb0a
3 files changed
+101
-1
No files matched your search
@@ -602,7 +602,11 @@ only `vaultik-destination.txt` stops such a backup, and only while the local
|
||||
index holds snapshots.
|
||||
|
||||
**Rclone** (`rclone://remote/path`): Uses rclone's 70+ supported cloud
|
||||
providers. Requires rclone to be configured separately (`rclone config`).
|
||||
providers. Requires rclone to be configured separately (`rclone config`). The
|
||||
path after the remote name is relative: rclone resolves it on the remote, for
|
||||
example against the login directory on sftp. A second slash makes it absolute,
|
||||
as in `rclone://remote//srv/backup`. A remote of type `local` needs an absolute
|
||||
path; a relative one is refused.
|
||||
|
||||
An upload cut off part-way leaves nothing under the object's name on S3, which
|
||||
shows an object only once its upload has completed, and on the local filesystem
|
||||
|
||||
Reference in new issue
Block a user