Deployment guide

Use the release toolchain: Node 22.23.3 and pnpm 11.2.2. Deploy from the matching lockfile for each package.

Application

Build from the repository root with pnpm build. Configure the required Supabase public values, server-only service credential, canonical application origin, intended registration controls and worker/housekeeping secrets.

Production app origin is https://helm.neuroom.io . The public landing is /welcome; root is a private financial view after sign-in.

Inspect the target’s schema and migration history. Apply only required approved forward changes sequentially, then verify permissions, financial balance and affected API behavior.

Authentication and mail

Configure provider Site URL and allowed callback/recovery destinations for the canonical app origin. Preserve safe relative return paths. Test actual signup, sign-in and session retirement.

The public reviewer-facing product uses open registration. Confirmation and recovery email require working provider mail transport; accepted requests alone do not establish delivery. Configure and verify mail before depending on those flows.

Documentation

Use base directory documentation, its frozen lockfile and netlify.toml. The build compiles Next.js and runs Pagefind. No database credentials belong in the docs environment.

Set NEXT_PUBLIC_HELM_APP_URL to https://helm.neuroom.io  and NEXT_PUBLIC_HELM_DOCS_URL to https://helm-docs.neuroom.io . Verify both reciprocal links and per-page canonical metadata.

Scheduled services

Import processing, housekeeping and quote refresh need configured server authorization and actual invocation. Verify the deployed schedule and provider availability.

Hosted acceptance

Check public/docs navigation, search, signup, a fresh owned first account/balance, optional recording, import preview/consent, failure recovery, logout and Back privacy. Use disposable exact fixtures and verify their cleanup. Keep source, compiled and hosted results separate.