Refuse a relative index_path at config load (closes #430)
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:
sneak committed 2026-11-11 04:23:56 +00:00
1 parent d8d13d1c8b
commit 75a9ef0889
4 files changed
+73 -1

No files matched your search

+2 -1
View File
@@ -276,7 +276,8 @@ storage_url: ""
# Hostname used in snapshot IDs. Default: system hostname.
# hostname: myserver
# Path to the local SQLite index database.
# Path to the local SQLite index database. 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