scripts/products/accounts.sh (backup with pg_dump, build with the shared packages, PM2, export, keep, failed-migration recovery); accounts in SUPPORTED_PRODUCTS so deploy updates it where a church has it. Env template in both places, PM2 example, export script, /api/health version from package.json. README, CHANGELOG, WHATS-NEW; the plan's changes while building and what's still to do. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
Accounts
The church's sign-in for every Cross Code product (ROADMAP-v3 §3, phase 3; plan and decisions in
docs/ACCOUNTS-1.0-PLAN.md). A small OpenID Connect provider per
church at accounts.<address>: people sign in once and are signed in to all the church's products,
coming back to the page they started on. Members never see it as a product; admins manage people,
sign-in settings, linked products and the church profile here.
backend/: Express + oidc-provider 9 + Prisma (ES modules).npm run dev,npm test(Node's test runner through tsx: the whole app against an in-memory database, with a test product on openid-client),npm run build.frontend/: Next.js 16 pages (sign-in steps, account page, admin, setup), strict CSP with a nonce per page, the church's colours from its profile.- Roles stay in each product: Accounts only knows who someone is (plan §2, "Roles stay in each product").
- Products sign in with
@crosscode/auth-client(packages/auth-client).
Local development: Postgres in backend/.env (DATABASE_URL, ACCOUNTS_URL=http://localhost:3200,
LINKS_ALLOW_PRIVATE=true), npx prisma migrate deploy, then npm run dev in both folders (the
frontend runs on 3200 with next dev -p 3200 and sends /api to the backend on 5200).