DJP d2271f9cf3 Deploy scripts: resolve repo root from script location ... The previous BACKEND_DIR_V2=/opt/social-reporting-v2 hardcode failed on the production host because we did an in-place cutover: V1 and V2 share a single checkout at /opt/social-reporting. ./v2/deploy/deploy-v2.sh exited immediately with "V2 dir not found". Both deploy-v2.sh and rollback-to-v1.sh now derive their repo root from the script's own location, so they work whatever the parent directory is named. setup-v2.sh is left alone — it's the first-time provisioner and creating /opt/social-reporting-v2 from scratch is still a fine default for greenfield installs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-29 21:15:22 -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	deploy: chown briefs/ to uid 1000 so container can write per-report dirs	2026-04-29 20:06:56 -04:00
deploy-v2.sh	Deploy scripts: resolve repo root from script location	2026-04-29 21:15:22 -04:00
rollback-to-v1.sh	Deploy scripts: resolve repo root from script location	2026-04-29 21:15:22 -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