378687fe5f
The Dove demo brief failed at Stage 3 with "Spent $0.00 across 0 scrapes"
— Stage 2 didn't actually invoke Apify even once. Two failure modes were
silent:
1. APIFY_LIVE_APPROVED is not 'true' in the container env, so every
runActor() call returns {items: [], status: 'DRY_RUN'} with no spend
log entry. Stage 2 happily writes empty pass1_videos.json and writes
its sentinel; Stage 3 then can't tell why.
2. seeds.json has zero hashtags + zero handles + zero search_terms (a
degenerate Stage 1 result), so the Stage 2 priority loop has nothing
to iterate.
Now Stage 2 throws fast on both, before scheduling any work:
- "Apify is in DRY-RUN mode but brief budget > 0. Set APIFY_LIVE_APPROVED=true
in v2/.env, restart V2, click Force re-run."
- "seeds.json contains zero hashtags/handles/search_terms. Click Force re-run
to regenerate Stage 1."
Both messages flow through to the Reports detail page failure panel via the
existing error_message COALESCE plumbing.
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