From 0f6c7a091285e2c96f857441e3497706096878f9 Mon Sep 17 00:00:00 2001 From: Vuong Hoang Date: Tue, 6 Oct 2026 15:38:21 -0700 Subject: [PATCH] feat(restic/irv-ml1): exclude arbo incognito uploads from the nightly backup comfy-dev's ask for Prime's arbo 'incognito' runs: incognito uploads and chained images are written to /worktank/comfyui/basedir/input/incognito-* and swept after a TTL. input/ is a backup source, so one alive at 01:00 would be kept for up to 3 years. Verified on irv-ml1: resticprofile show lists the exclude, and a restic dry-run of input/ skips an incognito-* canary while keeping a control canary. --- configs/restic/irv-ml1/profiles.yaml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/configs/restic/irv-ml1/profiles.yaml b/configs/restic/irv-ml1/profiles.yaml index 0da0eac..ca792e5 100644 --- a/configs/restic/irv-ml1/profiles.yaml +++ b/configs/restic/irv-ml1/profiles.yaml @@ -82,6 +82,12 @@ default: - /worktank/parakeet/models - /worktank/cosyvoice/input - /worktank/cosyvoice/output + # arbo "incognito" runs (comfy-dev, Prime's ask, 2026-10-06): uploads and + # chained images land in input/ as incognito-* and are swept after a TTL + # (default 1 h). input/ IS in source, so without this a file still alive at + # the 01:00 run would sit in the repo for up to 3 years. Incognito outputs go + # to output/arbo-incognito/, which is already covered by the output exclude. + - /worktank/comfyui/basedir/input/incognito-* # Docker internals we never want in a backup - /var/lib/docker/volumes/backingFsBlockDev - /var/lib/docker/volumes/metadata.db