3e71df8a79
The 1000 likes / 10000 plays defaults are calibrated for top-of-funnel beauty/fitness scrapes; in narrower TikTok niches almost every video lands below them and Stage 2 returns 0 keepers. Defaults dropped to 100 likes / 1000 plays across: - server/schemas/brief.ts (Zod default) - db/init.sql (column default for new DBs) - examples/dove-demo-brief.json - operator-app's brief-form initial values - operator-app's "Load Dove demo" inline brief Stage 3 empty-pass1 error now reads pass1/spend_log.json and reports the actual scrape breakdown — total $ spent, total raw videos returned, and how many got dropped by each floor (zero-plays / min_plays / min_likes / min_stl_pct). So instead of a generic "lower the floor", the user sees: "Spent $5.42 across 7 scrapes; 1400 videos returned. Dropped: 12 zero-plays, 1305 below min_plays=10000, 31 below min_likes=1000." Existing briefs are unaffected (column default applies to NEW rows). For the in-flight Dove2 run the user can edit the brief and lower the floor, then click Retry pipeline. 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