fix(gitea,invidious): stop two secrets sharing one placeholder index

Both configs defined a second secret in a later section starting the numbering
over, so CFG_GITEA_METRICS_TOKEN_1 and CFG_GITEA_ADMIN_PASSWORD_1 both read
RANDOMIZEDPASSWORD1 — and the replacer generates one value per distinct
placeholder and seds every occurrence, so the two came out identical. Same for
Invidious's HMAC key and admin password. Predates the slot rename.

Currently latent, since neither admin password is consumed by anything, but it
would silently pair a live secret with whatever gets wired to the other key.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
librelad 2026-08-18 20:51:31 +01:00
parent 4eb5fa6434
commit ec98a83b48
2 changed files with 2 additions and 2 deletions

View File

@ -71,4 +71,4 @@ CFG_GITEA_PORT_2="gitea-service|ssh|random:22|private|tcp|false|false|false|Git
CFG_GITEA_AUTH_PROFILE=multi_user
CFG_GITEA_ADMIN_USER=
CFG_GITEA_ADMIN_EMAIL=
CFG_GITEA_ADMIN_PASSWORD_1=RANDOMIZEDPASSWORD1
CFG_GITEA_ADMIN_PASSWORD_1=RANDOMIZEDPASSWORD2

View File

@ -69,4 +69,4 @@ CFG_INVIDIOUS_PORT_1="invidious-service|webui|random:3000|public|tcp|false|true|
CFG_INVIDIOUS_AUTH_PROFILE=multi_user
CFG_INVIDIOUS_ADMIN_USER=
CFG_INVIDIOUS_ADMIN_EMAIL=
CFG_INVIDIOUS_ADMIN_PASSWORD_1=RANDOMIZEDPASSWORD1
CFG_INVIDIOUS_ADMIN_PASSWORD_1=RANDOMIZEDPASSWORD2