Found by the acceptance test (#418), testing rclone destinations on next at d747dde.
What is missing
The README's rclone section says only "Requires rclone to be configured separately (rclone config)". It does not say:
that vaultik reads the file the rclone tool reads (by default ~/.config/rclone/rclone.conf on Linux), so the rclone tool is not needed once that file exists;
that RCLONE_CONFIG names another file; the environment-variable list leaves it out;
that a host restoring from an rclone destination needs that file, since it holds the destination's credentials; the "restoring on another machine" section shows only the S3 settings.
What should happen
The rclone section and the environment-variable list say these three things.
Model: opus-5-5
Found by the acceptance test (https://git.eeqj.de/sneak/vaultik/issues/418), testing rclone destinations on `next` at `d747dde`.
**What is missing**
The README's rclone section says only "Requires rclone to be configured separately (`rclone config`)". It does not say:
- that vaultik reads the file the `rclone` tool reads (by default `~/.config/rclone/rclone.conf` on Linux), so the `rclone` tool is not needed once that file exists;
- that `RCLONE_CONFIG` names another file; the environment-variable list leaves it out;
- that a host restoring from an rclone destination needs that file, since it holds the destination's credentials; the "restoring on another machine" section shows only the S3 settings.
**What should happen**
The rclone section and the environment-variable list say these three things.
Model: opus-5-5
clawbot
self-assigned this 2026-11-19 08:03:27 +01:00
README now documents the rclone config file, RCLONE_CONFIG, and the file's role when restoring on another machine: #470 (branch issue-469-readme-rclone-config).
Model: opus-5-5
README now documents the rclone config file, `RCLONE_CONFIG`, and the file's role when restoring on another machine: https://git.eeqj.de/sneak/vaultik/pulls/470 (branch `issue-469-readme-rclone-config`).
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found by the acceptance test (#418), testing rclone destinations on
nextatd747dde.What is missing
The README's rclone section says only "Requires rclone to be configured separately (
rclone config)". It does not say:rclonetool reads (by default~/.config/rclone/rclone.confon Linux), so therclonetool is not needed once that file exists;RCLONE_CONFIGnames another file; the environment-variable list leaves it out;What should happen
The rclone section and the environment-variable list say these three things.
Model: opus-5-5
README now documents the rclone config file,
RCLONE_CONFIG, and the file's role when restoring on another machine: #470 (branchissue-469-readme-rclone-config).Model: opus-5-5