32d80ff07e
Two issues addressed: 1) Delete brief was awkward — only on the detail page, only for admin/owner, and the on-disk briefs/<id>/ tree was orphaned even after a successful DB delete. Server policy is now: - team owner / admin: delete any brief in team - team editor: delete only briefs they own - team viewer: cannot delete - super-admin: bypass Plus: refuses to delete if a non-terminal pipeline run is active for the brief, and rm -rf's briefs/<id>/ after the FK cascade so scrape data, datasets and dashboards don't pile up. Operator UI: per-row Delete button on the briefs list page (with confirm) for users who have delete rights on each brief; detail-page rule loosened to match the server's editor-owner policy. 2) Pipeline error messages were being clobbered. The server's child-on-exit handler called finishReport() unconditionally, overwriting the actual error the pipeline's main()-catch had just written. Now we use a COALESCE update that only sets error_message when it's still NULL — so the real failure (e.g. "Stage 3: pass1_videos.json is empty…") wins over the generic "Pipeline exited with code 1". Stage 3's empty-pass1 error message is also now diagnostic: it lists the brief's current engagement-floor values and suggests what to lower. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| v2 | ||
| .gitignore | ||
| DEVELOPER_BRIEF_V2.md | ||
| README.md | ||
Social Reporting
V2 lives in v2/. All commands run from there.
cd v2
docker compose -f docker-compose.v2.yml --env-file .env up -d --build
npm install
npm test # 62 unit tests
npm run pipe seed --report <brief-id>
For the full V2 spec see DEVELOPER_BRIEF_V2.md.
Deploying V2 over an existing V1 install
If V1 is already deployed at /opt/social-reporting, cut over in place:
ssh you@optical-dev.oliver.solutions
cd /opt/social-reporting
git pull origin main # pulls in v2/, removes V1 dirs
bash v2/deploy/cutover-in-place.sh # stops V1, migrates secrets, starts V2
The script prompts before doing anything destructive, migrates
APIFY/Anthropic/Azure secrets from V1's .env into a fresh v2/.env,
swaps the Apache conf to V2's, and starts the V2 docker stack. It also
prompts for the email that will be auto-promoted to super-admin on first
SSO sign-in (BOOTSTRAP_SUPER_ADMIN_EMAIL).
The Azure-registered redirect URI
https://optical-dev.oliver.solutions/social-reports/login.html is
preserved by V2 (Vite base: /social-reports/, React Router basename,
and an explicit /login.html route alias).
V1 archive
V1 source is preserved on the v1-archive branch (frozen at the last V1
commit) and is no longer kept on the deployed server. To roll back from
V2 to V1, the rollback script will re-clone v1-archive if needed:
# On the server
export REPO_URL="https://x-token-auth:YOUR_TOKEN@bitbucket.org/zlalani/social-reporting-tool.git"
bash /opt/social-reporting-v2/v2/deploy/rollback-to-v1.sh
To inspect or check out V1 source locally:
git checkout v1-archive