Document the migration/seed/API/web workflow in a root README, add an API e2e smoke test that always checks /api/health and additionally exercises the real DatabaseModule/seeded data plus the arrivesAt validation rejection when DATABASE_URL is available, and add a `test:e2e` root script. Also fix `.env` loading so the documented root-level `.env` is actually found: `main.ts` never loaded dotenv at all, and `data-source.ts` loaded it relative to `process.cwd()`, which is `apps/api` (not the repo root) whenever npm runs a `--workspace` script. Both now resolve the repo-root `.env` explicitly. Also narrowed the CLI migrations glob to numeric-prefixed files so it no longer tries to load the colocated `*.migration.spec.ts` as a migration. Verified end-to-end against a real PostgreSQL instance: migrate, seed twice (idempotent), start the API, and exercise every documented route including a rejected POST /api/travel body containing arrivesAt. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
13 lines
506 B
Plaintext
13 lines
506 B
Plaintext
# Copy this file to `.env` (repo root) and adjust as needed. See README.md
|
|
# for the full local setup workflow (install, migrate, seed, run api/web).
|
|
NODE_ENV=development
|
|
PORT=3000
|
|
|
|
# Requires a reachable PostgreSQL server with a database named `ashen_realms`
|
|
# owned by this user/password (or your own local equivalent connection string).
|
|
DATABASE_URL=postgresql://ashen:ashen@localhost:5432/ashen_realms
|
|
|
|
JWT_ACCESS_SECRET=change-me
|
|
JWT_REFRESH_SECRET=change-me-too
|
|
JWT_ACCESS_TTL=15m
|
|
JWT_REFRESH_TTL=30d |