Self-hosting

​

Requirements

• Node.js 20+
• pnpm
• PostgreSQL 16+ (Supabase works great)

​

Environment variables

Solana chains/RPC/program id are not env. They live in the chain registry (DB), seeded by pnpm db:seed and edited in the workspace admin (GET /v1/chains, POST /v1/admin/chains). RPC API keys, if any, must be public or proxied — the registry is served to clients as-is.

​

Fiat (DOKU Checkout + internal ledger)

​

Local development with Docker

docker compose up -d          # Postgres
pnpm install
pnpm db:migrate               # apply Prisma migrations
pnpm dev                      # API on http://localhost:3301, docs on http://localhost:3300

​

Deploy to Vercel + Supabase

1. Supabase — create a project, then run migrations against it (use the session pooler, port 5432, for migrations):
   DATABASE_URL="postgresql://postgres.<ref>:<password>@aws-0-<region>.pooler.supabase.com:5432/postgres" \
     pnpm --filter @peridotvault/pid-api db:deploy
   
2. Vercel — API (apps/api/vercel.json is already configured for serverless). Add a project rooted at apps/api and set these env vars: DATABASE_URL (transaction pooler, port 6543, ?pgbouncer=true), JWT_ACCESS_SECRET, JWT_REFRESH_SECRET, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_CALLBACK_URL, COOKIE_SECURE=true, COOKIE_SAMESITE, CLIENT_SUCCESS_URL, CORS_ORIGINS.
3. Mintlify — docs (canonical; the board user deploys manually). The Mintlify source lives in apps/docs (docs.json + pages + openapi.yaml). In Mintlify: connect the peridot-id repo, set the docs path to apps/docs, and attach custom domains docs.peridot.id (prod) + sandbox.docs.peridot.id (sandbox) via CNAME at Hostinger. The legacy Fumadocs site (apps/docs) keeps serving the old pid.peridotvault.com/docs* paths until cutover; at cutover it lands a redirect old-docs → the Mintlify host.
4. Attach your custom domains and point DNS at Vercel.

​

Production build

pnpm build
pnpm --filter @peridotvault/pid-api db:deploy
pnpm --filter @peridotvault/pid-api start

​

Legacy-database migration notes

1. Email-duplicate audit — a non-null email is unique (one email = one PID). Resolve collisions before migrating (the uniqueness index fails otherwise):
   SELECT lower(email) AS email, count(*), array_agg("pid")
   FROM identity_credentials
   WHERE email IS NOT NULL
   GROUP BY lower(email)
   HAVING count(*) > 1;
   
2. Deploy with pnpm --filter @peridotvault/pid-api db:deploy (same flow as the Supabase steps above).
3. No backfill. Existing users get no wallet rows — they are created only by explicit user action (POST /v1/account), so nothing is silently created for existing accounts.