From aae3e30843f54406244b637073aaf5e9ccc6b1d3 Mon Sep 17 00:00:00 2001 From: ginnoir Date: Tue, 2 Jun 2026 19:12:34 -0500 Subject: [PATCH] fix(deploy): separate reactive resume auth_secret from famapp MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - rename AUTH_SECRET to RESUME_AUTH_SECRET in production .env and compose app service — famapp's AUTH_SECRET is now unambiguous - remove orphaned stale AUTH_SECRET entry from .env - apply-compose.ps1: pull + restart famapp immediately after pushing compose rather than waiting for watchtower; uses dc alias via bash -ic - update .env.production.example to reflect corrected variable names --- .env.production.example | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.env.production.example b/.env.production.example index 4a21816..98130d1 100644 --- a/.env.production.example +++ b/.env.production.example @@ -18,8 +18,8 @@ FAMAPP_DB_PASSWORD=replace-with-strong-password FAMAPP_DB_NAME=famapp # Auth.js session secret — generate with: openssl rand -base64 32 -# NOTE: the monolith .env also uses AUTH_SECRET for Reactive Resume. -# Docker Compose uses the last occurrence. Keep famapp's entry last. +# NOTE: Reactive Resume uses RESUME_AUTH_SECRET; AUTH_SECRET is famapp-only. + AUTH_SECRET=replace-with-openssl-rand-base64-32 # OIDC provider (Authentik) — fill in after bootstrapping Authentik