From 9496c701554b2d57bd2cc3ad98a306f15ea17826 Mon Sep 17 00:00:00 2001 From: twotalesanimation <80506065+twotalesanimation@users.noreply.github.com> Date: Fri, 21 Aug 2026 13:54:30 +0200 Subject: [PATCH] Pass SHOTS_API_KEY through to the app container The import-shots feature calls review.twotalesvfx.com from a server action that reads process.env.SHOTS_API_KEY. That variable existed only in the local gitignored .env, and the compose file passed just DATABASE_URL, NEXTAUTH_SECRET and NEXTAUTH_URL to the app service. In production the key was therefore undefined, so the action threw before issuing any request -- and because Next.js masks server-action errors in production, the UI showed a generic failure that looked like a network or CDN problem rather than missing configuration. Interpolate SHOTS_API_KEY from the deploy environment instead of hardcoding it, so the secret stays out of the repo. The :? guard makes compose abort with an explanatory message when the variable is missing, rather than silently starting an app that cannot import shots. Co-Authored-By: Claude Opus 5 --- docker-compose.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/docker-compose.yml b/docker-compose.yml index c6121df..5c4648e 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -32,6 +32,7 @@ services: DATABASE_URL: postgresql://postgres:postgres@postgres:5432/xbid NEXTAUTH_SECRET: hZTKvtZtchjbJulsVE8Kf5YPLibR619JoK/z7vO2i/s= NEXTAUTH_URL: https://xbid.twotalesvfx.com + SHOTS_API_KEY: ${SHOTS_API_KEY:?SHOTS_API_KEY must be set in the .env file next to docker-compose.yml} depends_on: postgres: