Getting Started

Orochia is a TypeScript monorepo (npm workspaces): the Next.js web app in apps/web and three packages — db (Drizzle schema, migrations, seed), media (Bunny Stream, Tus, signed URLs) and payments (gateway adapters, ledger).

1. Prerequisites

2. Run it

git clone https://github.com/krizaka/orochia.git && cd orochia
npm install
npm run setup     # .env (generated SESSION_SECRET) · PostgreSQL 16 · migrations · seed
npm run dev       # http://localhost:3000

npm run setup is idempotent. OROCHIA_DEMO_MODE=true (the .env.example default, ignored in production) lets the login page offer the seeded accounts and settles unlocks immediately when no payment gateway is configured.

3. Seeded accounts

These exist only in the development seed — production starts empty. The Development guide describes what each account demonstrates and the database commands (db:status, db:reset, db:studio, backups).

4. The admin console

The operator console is a separate repository, krizaka/orochia-admin:

git clone https://github.com/krizaka/orochia-admin.git && cd orochia-admin
npm install
OROCHIA_API_URL=http://localhost:3000 npm run dev -- -p 3001     # sign in with the administrator account

5. Quality gates

Every change must pass, locally and in CI:

npm run check          # lint · type-check · unit tests · generated docs up to date
npm run build
npm run test:e2e       # feature scenarios, on a freshly reset database with the app running

Where next

• Development guide — everyday commands, schema changes, seed, reset and backups.
• Database reference — every table, index and foreign key, generated from the schema.
• Architecture — how access, payments, the ledger and compliance fit together.
• Media Pipeline — direct-to-Bunny uploads and signed playback.
• API Reference — every endpoint and the rule that guards it, generated from the code.
• Deployment & Operations — configuration, gateway webhooks and DigitalOcean App Platform.