social-reporting-tool/v2/deploy
DJP 7d70c0c155 Bake VITE_AZURE_* into the SPA at docker build time; sweep V1 leftovers in cutover
Two issues from the first server cutover:

1. SPA loaded white-on-black blank because import.meta.env.VITE_AZURE_TENANT_ID
   and VITE_AZURE_CLIENT_ID were undefined at runtime. Vite reads VITE_* at
   *build time* and inlines them into the bundle; passing them only as
   runtime container env vars is too late.
   - Dockerfile.v2: declare ARG VITE_AZURE_TENANT_ID, VITE_AZURE_CLIENT_ID,
     VITE_BASE; export as ENV before `npm run build`.
   - docker-compose.v2.yml: forward AZURE_TENANT_ID / AZURE_CLIENT_ID /
     VITE_BASE through `build.args` so the cutover .env values reach Vite.

2. cutover-in-place.sh stopped V1 with `-p social-listening`, but V1's actual
   compose project name was `social-reporting` (parent dir). Old V1 containers
   were left running. Now we try both project names AND sweep by container
   name pattern (anything matching social-listening or social-reporting-db-1
   that isn't a V2 container).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-29 19:00:15 -04:00
..
apache-social-reports-v2.conf Add V2: multi-team social-reporting platform with manifest-gated linking 2026-04-29 17:39:07 -04:00
cutover-in-place.sh Bake VITE_AZURE_* into the SPA at docker build time; sweep V1 leftovers in cutover 2026-04-29 19:00:15 -04:00
deploy-v2.sh Add V2: multi-team social-reporting platform with manifest-gated linking 2026-04-29 17:39:07 -04:00
rollback-to-v1.sh Wire SPA + SSO redirect URI to /social-reports/ prefix; in-place cutover script 2026-04-29 18:40:38 -04:00
setup-v2.sh Wire SPA + SSO redirect URI to /social-reports/ prefix; in-place cutover script 2026-04-29 18:40:38 -04:00