vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

feat(restic/irv-ml1): exclude arbo incognito uploads from the nightly backup

Browse Source 
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.
This commit is contained in:
vh
2026-10-06 15:38:21 -07:00
parent ad939810e7
commit 0f6c7a0912
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
configs/restic/irv-ml1/profiles.yaml
+6
View File
@@ -82,6 +82,12 @@ default:
- /worktank/parakeet/models - /worktank/parakeet/models
- /worktank/cosyvoice/input - /worktank/cosyvoice/input
- /worktank/cosyvoice/output - /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 # Docker internals we never want in a backup
- /var/lib/docker/volumes/backingFsBlockDev - /var/lib/docker/volumes/backingFsBlockDev
- /var/lib/docker/volumes/metadata.db - /var/lib/docker/volumes/metadata.db