Skip to main content
Local development uses Node.js 22+, pnpm 9, Docker Compose, PostgreSQL, MinIO, Mailpit, and provider-safe demo behavior.

​
Start the stack

Open http://localhost:3000/login and choose a demo staff member.
Demo provider actions are labelled and must not be treated as live Discord or Roblox verification. Use a disposable local database for browser and API tests.

​
Verification commands

The API/database suite expects the explicitly seeded local test database. Browser tests create clearly named test records.

​
Useful boundaries

  • MOCK_PROVIDERS=true prevents real provider writes in the intended demo environment.
  • Public URLs and callback allowlists must match each local service.
  • Secrets belong in ignored environment files, never in client variables or fixtures.
  • Additive migrations must be applied before code that depends on their columns or constraints.

​
Documentation preview

From the Mintlify content directory:
Use the Mintlify CLI’s validation output to resolve broken links, invalid docs.json settings, and MDX parse errors before pushing documentation changes.

​
Guided walkthrough

Rodyne integration capability page used to validate a local environment

A usable environment must prove provider capability, not merely start its web processes.

The screenshot above is from the live Rodyne product. Use it to orient yourself, but rely on the current record state and live provider checks when operating the workspace.

​
Operating procedure

1

Install and configure

Use the documented Node, package manager, database, Redis, and environment versions.
2

Apply the schema

Run migrations against the intended local database before starting services.
3

Start boundaries

Run web, API, auth, ingress, connect, dash, and worker with distinct ports and secrets.
4

Connect test providers

Use development Discord, Roblox, Stripe, and Studio resources only.
5

Exercise one durable flow

Create a job, let the worker execute it, and inspect the audit and read-back result.

​
Acceptance checks

​
Failure recovery

Avoid disabling validation to make a local stack start. A missing secret, origin, audience, or queue dependency often creates misleading downstream failures.

​
Continue the workflow

Architecture

Studio connector reference