Suggestions

A TanStack Start app with a tRPC API, served by Bun, backed by Postgres via Drizzle, with auth by Clerk.

Setup

1. Copy .env.example to .env and fill it in:
   • DATABASE_URL for your Postgres database
   • Clerk publishable/secret keys from the Clerk dashboard
   • ADMIN_EMAILS: verified email addresses allowed into the admin dashboard
2. bun install

The schema is defined with Drizzle in src/server/schema.ts. Apply migrations from drizzle/ with bun run db:migrate, and run bun run db:generate to create a migration after changing the schema. Run migrations with a schema owner credential; the production server can use a restricted data-only role.

Development

bun run dev applies migrations and starts the Vite dev server on port 3001.

Production

bun run db:migrate && bun run build && bun run start — the Bun server in server/index.ts serves /healthz, the built assets and the Start app. Supply the owner credential only to the migration command when using separate database roles.

For the host's container deployment, database provisioning and rollback, see deploy/README.md.

Runtime configuration

Server settings are validated with @t3-oss/env-core and Zod when they are read. Production builds need no runtime credentials. Invalid settings report their names without logging secret values; see .env.example for the deployment settings. Migration commands validate database settings independently of Clerk configuration.

Database tests

TEST_DATABASE_URL=postgres://... bun run test runs the env checks and five named Bun integration tests against an explicitly supplied disposable PostgreSQL service: repeatable migrations, restricted-role permissions, API validation/auth, and health-probe cancellation/recovery, plus application connection reuse, idle retirement and reconnection. Fixtures are created and removed by test hooks, and modified runtime environment values are restored after the suite. The deployment receiver continues to run through its separate Node test command.