No description
Find a file
2026-10-23 10:38:12 +08:00
my-node-server initial commit 2026-10-23 10:36:22 +08:00
next-frontend initial commit 2026-10-23 10:36:22 +08:00
ocr-service initial commit 2026-10-23 10:36:22 +08:00
CUTOVER.md initial commit 2026-10-23 10:36:22 +08:00
README.md initial commit 2026-10-23 10:36:22 +08:00

Payment Tracker v2

Rewrite of the Flask payment tracker (../payment-tracker) into a modern React stack.

Part Stack Dir
Frontend Next.js 16 (App Router) + axios + TanStack Query next-frontend/
Backend API Node + Express 5 + Prisma + MySQL, JWT, {success,message,data} envelope my-node-server/
OCR / AI-fill Python FastAPI side-service (pytesseract + Ollama/DeepSeek), reused from the Flask code ocr-service/

Quick start

See CUTOVER.md for the full runbook. Short version:

# 1. backend + DB
cd my-node-server && cp .env.example .env   # set DATABASE_URL, JWT secrets, ADMIN_PASSWORD
npx prisma migrate dev --name init && npm run seed && npm run dev   # :5000

# 2. OCR service (optional for core flows)
cd ../ocr-service && pip install -r requirements.txt && uvicorn main:app --port 8000

# 3. frontend
cd ../next-frontend && npm run dev          # :3000

Why this shape

The original is a relational, OCR-heavy Flask monolith. We kept the OCR/LLM logic in Python (a thin side-service) instead of reimplementing it in Node, used Prisma+MySQL because the domain is relational (12 linked tables — not the Mongoose/Mongo the frontend boilerplate assumed), and preserved the original DB column names so the data migration is a straight copy. Werkzeug password hashes verify as-is, so existing users keep their passwords.

Each sub-project has its own CLAUDE.md.