Getting Started

Prerequisites

Database commands run inside Docker. You do not need a host node_modules install solely to migrate or seed.

Clone / open the repository.
Copy .env.example to .env.
Add the required /etc/hosts entries (see the root README.md). Include both 127.0.0.1 and ::1 lines — IPv4-only entries cause ~5s delays on macOS when clients attempt AAAA lookups for .test hostnames.
Start the Docker development stack:
```
pnpm dev
```
This runs docker compose -f compose.yml -f compose.dev.yml up.
With the stack running, apply the schema and seed Luigi / Mario:
```
pnpm db:migrate
pnpm db:seed
```

Service	URL
Storefront	http://storefront.bytebite.test
Dashboard	http://dashboard.bytebite.test
API (direct)	http://api.bytebite.test
Docs	http://docs.bytebite.test
Luigi	http://luigi.bytebite.test
Mario	http://mario.bytebite.test
Unknown restaurant	http://unknown.bytebite.test
Same-origin API	`http://<app-host>/api/...`
MinIO console	http://localhost:9001
Traefik dashboard	http://localhost:8080
Drizzle Studio	http://localhost:4983 (`pnpm db:studio`)

Direct API example: http://api.bytebite.test/health

Same-origin examples (Traefik strips /api before Fastify):

Command	Description
`pnpm dev`	Start the Docker dev stack
`pnpm dev:down`	Stop the dev stack
`pnpm dev:rebuild`	Rebuild images and start the stack
`pnpm build`	Build all apps/packages (Turborepo, host)
`pnpm lint`	Lint the monorepo
`pnpm typecheck`	Typecheck the monorepo
`pnpm test`	Run unit/integration tests (Vitest)
`pnpm db:generate`	Generate Drizzle migrations (API container; stack running)
`pnpm db:migrate`	Apply migrations (API container; stack running)
`pnpm db:seed`	Seed the local database (API container; stack running)
`pnpm db:studio`	Drizzle Studio at http://localhost:4983

The API does not auto-migrate on startup. pnpm db:* is the documented workflow.

.env DATABASE_URL uses localhost (host network).
Compose overrides DATABASE_URL inside the API container to hostname postgres.
Compose overrides S3_ENDPOINT inside the API container to http://minio:9000.
Storefront and Dashboard browser bundles do not receive server secrets. Browser API calls use same-origin /api.
Docker dev uses anonymous volumes for apps/docs/.next and apps/storefront/.next so host-side pnpm build output does not corrupt the in-container Next.js dev/Turbopack cache. After adding new Fumadocs MDX pages, restart the docs service if the dev server was already running when the file was created.

Fastify is the central backend/business boundary. Storefront and Dashboard must not access PostgreSQL directly.
packages/domain is infrastructure-independent.
No packages/ui; Dashboard shadcn components live at apps/dashboard/src/components/ui/.
No separate apps/admin; the initial ADMIN area is a protected section inside Dashboard.