Physio Trainer
Rehab routines your patients actually open. Physiotherapists manage customers and injury
cases, build routines and weekly plans from their own exercise library (videos, categories,
body areas), and share them through a clean link, with no patient account needed. Patients can
follow a guided workout, log sessions and pain, and download a branded PDF.
Status: sign-in, onboarding and profile (spec 01) are built. Features are specified in
docs/specs/ and built one per session.
Stack
Next.js 16 (App Router) · TypeScript · Tailwind CSS v4 · shadcn/ui · Supabase (Postgres, Auth,
Storage) · Drizzle ORM · next-intl · Vitest · Playwright. See
docs/architecture.md.
Getting started
Requirements: Node 24 (see .nvmrc), pnpm 10, Docker (for local Supabase).
pnpm install
pnpm db:start # local Supabase in Docker
cp .env.example .env.local
# Copy PUBLISHABLE_KEY and SECRET_KEY from `pnpm exec supabase status -o env` into
# NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY and SUPABASE_SECRET_KEY in .env.local
pnpm dev # http://localhost:3000, sign-in emails land in Mailpit (http://127.0.0.1:54324)
Scripts
| Script | What it does |
|---|
pnpm dev / build / start | Next.js |
pnpm check | Lint, typecheck, Prettier check, unit tests |
pnpm test / test:watch | Vitest |
pnpm test:int | Integration tests against local Supabase (RLS, triggers, queries) |
pnpm test:e2e | Playwright (desktop + mobile), builds and serves on port 3100 |
pnpm db:start / db:stop / db:reset | Local Supabase |
pnpm db:generate | Generate a migration from the Drizzle schema |
pnpm db:studio | Drizzle Studio |
Deployment
Vercel deploys main to production through its GitHub integration. vercel.json turns off
deployments for every other branch: there is no separate preview database, and the env vars
are set for Production only. Set them in Vercel from .env.example, with DATABASE_URL on
Supabase's transaction pooler (port 6543). NEXT_PUBLIC_* values are inlined at build time, so
redeploy after changing one.
Hosted Supabase setup
Local config lives in supabase/config.toml; a hosted project needs the same settings in the
dashboard:
- Migrations: the
migrate job in .github/workflows/ci.yml applies pending migrations on
every push to main, after all checks pass (it does nothing when none are pending). One-time
setup: create a GitHub environment named production and add a SUPABASE_DB_URL secret to
it, using the session pooler connection string (Project Settings → Database → Connection
string, port 5432, user postgres.<ref>, password percent-encoded). The direct host is
IPv6-only and the transaction pooler (6543) can't run migrations. The first run also creates
the auth.users trigger that gives every new user a physios row. To apply by hand:
pnpm exec supabase db push --db-url "<session pooler url>". Vercel deploys main in parallel,
so keep migrations additive (see docs/architecture.md).
- Data API: disable it (Project Settings → Data API). The app only talks to Postgres
through Drizzle on the server.
- Auth → URL configuration: Site URL = the app URL; add
<app URL>/auth/** to the
redirect URLs. A missing redirect URL breaks magic links (they fall back to the Site URL).
- Auth → Email templates: paste
supabase/templates/magic_link.html into both "Magic
Link" and "Confirm signup", and set both subjects to
Tu link para ingresar · Your sign-in link — Physio Trainer (the subjects in
supabase/config.toml only apply locally). Re-paste whenever the template changes (it
became bilingual in spec 17).
- Auth → SMTP: configure a real SMTP provider before launch; the built-in sender is
rate-limited and only delivers to project team members. Until then, set
NEXT_PUBLIC_AUTH_EMAIL_ENABLED=false (with Google enabled) to hide the magic-link form.
- Google (optional): enable the provider with the Google Cloud client id/secret, then set
NEXT_PUBLIC_AUTH_GOOGLE_ENABLED=true in the app's environment.
Project docs
