From 0487e218046388ef9f06c4ebf44afce55b6bb1fc Mon Sep 17 00:00:00 2001
From: Aleksandar Grbic <hi@aleksandar.xyz>
Date: Wed, 24 Jun 2026 10:36:16 +0200
Subject: [PATCH] fix(tsforge): route app-feature env to compose
 api.${STACK}.env

The compose api service loads its env from infra/compose/compose/api.dev.env
(dev) / api.prod.env (prod) via docker-compose.yml `env_file`. apps/api/.env is
only read by standalone `bun run dev`, never by the compose stack the scaffold
wizard boots. Point envFileDefault at the compose api env file with a ${STACK}
placeholder the wizard resolves (smoke shares the dev file).
---
 .tsforge/scaffold-manifest.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.tsforge/scaffold-manifest.json b/.tsforge/scaffold-manifest.json
index 87168c2..3ed69fb 100644
--- a/.tsforge/scaffold-manifest.json
+++ b/.tsforge/scaffold-manifest.json
@@ -5,7 +5,7 @@
   "repo": "https://github.com/boringstack-xyz/boringstack",
   "renameParams": ["project", "ghcrOwner", "domain"],
   "alwaysOnServices": ["postgres", "valkey", "api", "ui", "api-migrate"],
-  "envFileDefault": "apps/api/.env",
+  "envFileDefault": "infra/compose/compose/api.${STACK}.env",
   "envFileByGroup": {
     "infra": "infra/compose/compose/.env",
     "identity": "infra/compose/compose/.env"