6 Commits

Include renames

Author	SHA1	Message	Date
clawbot	8b617efa63	Rotate a database target's archive monthly, daily or hourly (closes #379) ... A database target's rotation setting (none, monthly, daily or hourly) puts the UTC period of each event's receive time in its archive file name, so each file holds exactly its period's events. It is on the new webhook page and both target forms, and shown in the target list. Renames move every one of a target's files and move them all back if one fails. The sweep prunes one file at a time under the target's lock and deletes a rotated file it leaves empty. Download opens one file at a time, oldest period first, finding each again under the target's current name. The target list names the current file and totals all of them. Model: opus-5-5	2026-10-03 04:18:37 +02:00
clawbot	4915d60d8e	Route the delivery tests' gorm.Open through gormlog (closes #462) ... Six test-only gorm.Open calls in internal/delivery passed a bare gorm.Config, leaving the unfiltered idiom in the tree to be copied into production code, where every gorm.Open goes through gormlog.New. They now pass gormlog.New over a logger that discards, so no gorm.Open in the tree uses a bare gorm.Config. The stale sentence saying the tree has one test-only (*gorm.DB).Scan caller is corrected in the README and in the ParamsFilter comment: only tests call Scan, and what a test binds is fixture data. Test and documentation change only. Model: opus-5-5	2026-10-02 20:20:49 +02:00
clawbot	45bd7e9b94	Pin the close before the reopen in the archive sweep (closes #103) ... The archive sweep closes a target's archive connection before it reopens the file, and no test noticed if that close was removed, which would leak one SQLite connection per target per sweep. A test now keeps the connection from before a sweep that reopens the archive and requires it closed afterwards. The sweeper's query for database targets takes the sweep's context; a sweep whose context is done returns without an error line, so stopping is not logged as a failure, and a test pins that. The comment on the sweeper's cancel function gives the true reason it needs no lock: fx calls the stop hook only after the start hook has returned. Model: opus-5-5	2026-10-02 18:16:31 +02:00
clawbot	fd036774f9	Name each database target's archive for its webhook and target (closes #376) ... Each database target now writes its own archive file, archive-WEBHOOKNAME-TARGETNAME-TARGETID.db, named by delivery.ArchiveFileName, in place of one archive per webhook keyed on its UUID. Renaming a webhook or a target renames its archive files (with any -wal and -shm) before the new name is saved, never over an existing file, and moves every one back if a rename or the save fails. The webhook edit, the target edit and target creation share one lock so no two interleave. Deleting a webhook or target leaves its files on disk. Nothing looks for the old archive-WEBHOOKID.db files. The README gives the naming and the recovery steps. Model: opus-5-5	2026-10-02 13:28:49 +02:00
clawbot	2ee720a9af	Bound shutdown hooks by their stop context (closes #102)	2026-08-14 06:18:33 +02:00
clawbot	3e261d2f01	Evict archive writers on deletion and sweep idle archives (closes #89) (#95) ... Per-webhook archive writers are now evicted when the webhook or its last database target is deleted, and a background sweeper prunes expired rows from idle archives that no longer receive writes. Archive files themselves are never deleted.	2026-08-10 15:52:20 +02:00