v16: enable zoekt code search #76
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#76
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?
Tier 1 v16 follow-up (gated on #73 landing). v16 adds Zoekt as a first-class code-search engine (PR 8827):
[indexer] REPO_INDEXER_TYPE = zoekt. Verified embedded — an in-process Go library, no sidecar/extra container; Forgejo manages index shards in a directory (REPO_INDEXER_PATH, 512 MB max shard).Today we run without a repo indexer (code search limited to single-repo). Enabling Zoekt is an
app.ini.j2+ disk change only:/data/gitea/indexers/repos.zoekton the forgejo-data volume; current corpus fits comfortably, generic disk alerts cover it.REPO_INDEXER_ENABLED = true,REPO_INDEXER_TYPE = zoekt,REPO_INDEXER_PATHinapp.ini.j2; apply. — applied to prod 2026-07-18, forgejo restarted, shards built.bleve— deferred; zoekt kept (works, real hits). Revisit only if the explore.Code panic (#113) proves worse than the bleve alternative.Applied via PR #97. Known issue: some queries 500 (upstream Forgejo
explore.Codepanic) — tracked in #113. Product angle: instance-wide code search is a visible paying-user feature — worth a site/docs mention once #113 is resolved.