From 28911d55c81e7bda28ee57512e8663ec7488f378 Mon Sep 17 00:00:00 2001 From: sneak Date: Thu, 19 Nov 2026 08:42:05 +0000 Subject: [PATCH] Say how the path in an rclone:// URL is read Rebased onto next, where an rclone remote of type `local` refuses a relative path (https://git.eeqj.de/sneak/vaultik/issues/465) and the README says how the path is read. The rebase kept this PR's text, so the README's "rclone" section now carries those facts in its own words: the path is relative, a second slash makes it absolute, and a `local` remote refuses a relative path. Model: fable-5-2 --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index 2295d38..3bd754a 100644 --- a/README.md +++ b/README.md @@ -1097,6 +1097,13 @@ with `rclone config`. `vaultik` reads rclone's own config file. The URL takes no parameters and no credentials. +The path after the remote name is relative. Where it starts depends on the +storage service. On an SFTP server it starts in the login directory. A second +slash makes the path absolute, as in `rclone://remote//srv/backup`. + +A remote of rclone's type `local` writes to the machine's own disk. On such a +remote, a relative path is refused. + ### Interrupted uploads An upload that is cut off must not leave a partial object under the final name.