Refuse a relative index_path at config load (closes #430)
check / check (push) Successful in 11m12s
check / check (push) Successful in 11m12s
A relative index_path resolved against the working directory, so a backup run from another directory started from an empty index. Validate now refuses it, naming the value, with the same wording as the file:// storage_url check. ~ is still expanded first. The check sees the final value, so a relative VAULTIK_INDEX_PATH is refused too; an explicitly empty index_path is refused as well. Model: opus-5-5
This commit is contained in:
1 parent
d8d13d1c8b
commit
75a9ef0889
4 files changed
+73
-1
No files matched your search
@@ -295,6 +295,7 @@ storage_url: "rclone://myremote/path/to/backups"
|
||||
|
||||
# Path to local SQLite index database
|
||||
# This database tracks file state for incremental backups
|
||||
# It must be an absolute path; ~ is expanded
|
||||
# Default: the platform data directory, e.g.
|
||||
# macOS: ~/Library/Application Support/vaultik/index.sqlite
|
||||
# Linux: ~/.local/share/vaultik/index.sqlite
|
||||
|
||||
Reference in new issue
Block a user