How syedtazyeen/datum works
Main components
a. Frontend (Remix/React Router SSR)
b. Backend / Server-side API (Remix actions & loaders)
c. Database layer (Drizzle ORM + PostgreSQL)
d. Authentication service (Supabase Auth)
e. OCR & LLM external services (invoice parsing logic)
f. Session & state management (session storage/resolvers)
g. Static assets & build pipeline (Vite, public folder)
Relationships and data flows
• User browser ↔ Remix SSR (entry.client.tsx & entry.server.tsx)
• SSR routes (app/routes.ts & app/pages/…) invoke:
• Loaders (app/session/loaders.ts) for fetching data
• Actions (app/actions/*.ts) for mutations (auth-callback, invoice, onboard, etc.)
• Actions → Business logic (app/lib/*.ts) → Database (app/db/client.ts via Drizzle ORM)
• Authentication flows → Supabase client (app/supabase/client.ts)
• Invoice processing:
• File upload component (app/components/files/drag-upload.tsx) → server action
• Server action calls OCR/LLM (app/lib/invoice.ts) → returns structured data
• Data saved via Drizzle ORM into PostgreSQL
Architectural patterns & design principles
• Server-side rendering (Remix) with nested routing patterns (app/pages/(dashboard)/…)
• Layered architecture: UI → API actions → business-logic libraries → ORM → database
• Clean separation:
• UI components (app/components/ui & common)
• Domain logic (app/lib)
• Data access (app/db/api & client)
• Configuration (drizzle.config.ts, vite.config.ts, tsconfig.json)
• CI/CD / migrations: Drizzle migrations folder with snapshot & journal
Technologies, frameworks & libraries
• React 19 + Remix SSR + React Router config (react-router.config.ts)
• Tailwind CSS (app/app.css) + Radix UI (components/ui)
• Drizzle ORM (drizzle.config.ts, app/db/schema.ts) + PostgreSQL
• Supabase Auth (app/supabase/client.ts)
• Zod for request-payload validation (implied via lib/utils or lib/response)
• Vite for dev server & build (vite.config.ts)