No description
The drizzle/ folder was in .gitignore (line 34) — likely confused with the build 'out/' dir. Effect: migration SQL never reached the server on deploy, so the migration pipeline could never have worked. Only 7 of 18 files were ever force-tracked; 0000-0010 + most of manual/ were untracked. - Remove drizzle/ from .gitignore; document why it must be tracked - Archive legacy hand-rolled migrations 0000-0015 + manual/ to _archived_pre_baseline_2026-05-19/ (kept on disk; history retains old copies) - Archive stale meta/ (knew of only 3 of 16 migrations) - Baseline regeneration follows in subsequent commits |
||
|---|---|---|
| docker/init-db | ||
| docs | ||
| public | ||
| scripts | ||
| src | ||
| .dockerignore | ||
| .gitignore | ||
| CLAUDE.md | ||
| docker-compose.dev.yml | ||
| Dockerfile | ||
| drizzle.config.ts | ||
| next-env.d.ts | ||
| next.config.ts | ||
| package-lock.json | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| postcss.config.mjs | ||
| Project_tia.md | ||
| README.md | ||
| tsconfig.json | ||
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.