mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 19:01:54 +00:00
kevinveenbirkenbachandClaude Opus 5
6ca511a6f4
svc-registry-cache is the twin of the registry volume fixed in 1e5d2abb8: same /var/lib/registry target, same missing declaration, and the same claim in its own first line that the volume is backup-disabled. Matomo's tmp entry likewise already documents a regenerable Twig and session cache. Neither statement was true, because backup_volume.py keys on the declaration alone.
Also jellyfin's /cache, which sits beside the /config volume that stays backed up, and nextcloud's whiteboard tmp, whiteboard fontcache and talk recording tmp.
Left alone: gitlab's builds volume holds CI artifacts, which are reproducible but whose retention is a product decision, and the gitlab config templates, the cdn build script and the openldap ldif bind, which a name-based scan turns up but which are not caches.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
10 lines
277 B
YAML
10 lines
277 B
YAML
# nocheck: backup-service-flag pull-through cache content is re-fetchable; the volume is backup-disabled and the consumer permanently off
|
|
---
|
|
data:
|
|
type: volume
|
|
name: docker_registry_cache_data
|
|
backup: false
|
|
mounts:
|
|
- service: cache
|
|
target: /var/lib/registry
|