fix(local): repair the preview, broken since the bitborg rename #449
Inga granskare
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!449
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "fix/local-preview-rename-drift"
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?
make upinlocal/fails outright:The ADR 0039 rename moved
gitborg_domaintobitborg_domainingroup_varsand updatedapp.ini.j2, but leftlocal/vars.local.ymlbehind. The preview renders the prod template againstits own vars, so the template asked for a name its vars no longer defined.
Half-renamed rather than simply un-renamed. Line 77 of the same file already used
bitborg_domain; line 10 still definedgitborg_domain. Same shape as the ADR 0039 §7b textfilewriters, where
HELPandTYPEmoved to the new prefix and the sample line did not.Nothing noticed because the preview is a developer tool and is not exercised by CI. The only signal
is a person running
make up, and it stays broken until someone needs it, which is when they leastwant to debug it.
Verified, not assumed
make upnow completes and the stack serves. Checked in the running preview:16.0.2+gitea-1.22.0.https://www.bitborg.se/en/signup, sobitborg_www_domainrenders as its own comment promises ("footer links render exactly as inprod"). It previously said
www.gitborg.se.Also renamed the display-only
forgejo_app_name, which still readgitborg (local dev). Cosmetic,same drift.
Why this came up
Needed to verify the ADR 0038 concealment surfaces against Forgejo 16.0.2 for #447 without touching
production.
local/Makefilepins the floating16-rootless, so the preview runs 16.0.2 today, whichmakes it the right place for that check. Kept as its own change so the security bump in #447 stays a
two-line diff and reviews quickly.
Note for a follow-up, not fixed here
local/Makefilepinscodeberg.org/forgejo/forgejo:16-rootlessunder a comment reading "Keep insync with ansible/group_vars/all/vars.yml (forgejo_image*, postgres_image*)". It is a floating minor
where prod is pinned exact, so the two cannot be in sync by construction. Convenient for this task,
but the comment claims an invariant that does not hold, and that is the same class of thing as the
bug above. Worth deciding deliberately rather than leaving the comment wrong.
a33b31350dd0caf4ea66