Exclude the zoekt index from backups (derived, regenerable data) #189
Etiketter
Inga etiketter
area/backups
area/ci
area/control-panel
area/identity
area/infra
area/observability
area/payments
area/security
area/storage
area/web
blocked
needs-info
needs-triage
ready-for-implementation
type
bug
type
chore
type
docs
type
epic
type
feature
type
task
wontfix
Ingen milstolpe
Inget projekt
Inga tilldelade
1 deltagare
Notiser
Förfallodatum
Inget förfallodatum satt.
Beroenden
Inga beroenden satta
Referens
bitborg/bitborg-infra#189
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "%!s()"
Borttagning av en gren är permanent. Även om den borttagna grenen kan fortsätta existera en kort tid innan den faktiskt tas bort, kan det INTE ångras i de flesta fall. Vill du fortsätta?
The zoekt code-search index is derived data — fully rebuildable by re-indexing the repos — so it should not be in the age-encrypted backup archives (ADR 0022), same hygiene as caches.
Exclude the index path (
[indexer] REPO_INDEXER_PATH/ the zoekt data dir) from the backup role's tar. Benefits: smaller/faster backups + off-site storage savings, faster restore drills (ADR 0027), and never restoring a stale/corrupt index. Trade-off: search is degraded post-restore until Forgejo re-indexes (minutes–hours) — acceptable (search is non-critical;forgejo doctordoesn't need it).Zoekt is currently OFF (#165) so there's no index today — bake the exclusion in now so it's ready when re-enabled (behind the zoekt re-enable gate). Relates: #162, #165, ADR 0022/0027.