Daemon mode after 1.0: watch for file changes so frequent backups skip the full scan #204

New Issue

2026-09-25T11:54:33+02:00

clawbot commented

2026-09-25 11:54:33 +02:00

Owner's reasoning (sneak, on #94 (comment), 25 September 2026), verbatim:

option 1. daemon mode seems like a good idea bc of inotify so it can avoid full scans for frequent backups (eg hourly) but other than that it adds little value and in the usual use case where backups are run every 12 or 24 or 36 hours from cron it doesn't really matter.

Option 1 was: daemon mode comes after 1.0; delete the unreleased branch and keep its intent here so the design is not lost.

What it was

The branch feature/daemon-mode (tip 87acc05, "fix: add RunDaemon test, remove dead daemonWatcherBatchDelay constant") holds a long-running mode that watches the filesystem for changes and batches them, so a backup does not have to scan every file. Nothing on main depends on it; no command or document exposes it.

When to pick it up

After 1.0. Its value is for frequent backups, such as hourly, where a full scan each time is costly; for the usual runs from cron every 12 to 36 hours it adds little.

Model: opus-5-5

Owner's reasoning (sneak, on https://git.eeqj.de/sneak/vaultik/issues/94#issuecomment-103122, 25 September 2026), verbatim: > option 1. daemon mode seems like a good idea bc of inotify so it can avoid full scans for frequent backups (eg hourly) but other than that it adds little value and in the usual use case where backups are run every 12 or 24 or 36 hours from cron it doesn't really matter. Option 1 was: daemon mode comes after 1.0; delete the unreleased branch and keep its intent here so the design is not lost. ## What it was The branch `feature/daemon-mode` (tip `87acc05`, "fix: add RunDaemon test, remove dead daemonWatcherBatchDelay constant") holds a long-running mode that watches the filesystem for changes and batches them, so a backup does not have to scan every file. Nothing on `main` depends on it; no command or document exposes it. ## When to pick it up After 1.0. Its value is for frequent backups, such as hourly, where a full scan each time is costly; for the usual runs from cron every 12 to 36 hours it adds little. Model: opus-5-5

clawbot referenced this issue

2026-09-25 11:54:40 +02:00

Decide whether feature/daemon-mode is 1.0 scope #94

clawbot referenced this issue

2026-09-28 20:01:26 +02:00

Decide whether feature/daemon-mode is 1.0 scope #94

clawbot referenced this issue

2026-10-01 20:08:56 +02:00

List only after-1.0 work in the README roadmap #209

clawbot referenced this issue

2026-10-01 20:27:43 +02:00

List only after-1.0 work in the README roadmap #209