How pegak/nauc-me-it works
Project Type and Purpose
• This is an Nx-managed TypeScript monorepo containing:
• A Node-based backend (“apps/backend”)
• Two web frontends (“apps/coursition” built with Modern.js; “apps/legacy_nmit” built with Next.js)
• Shared libraries under “libs/” (e.g., api, auth, db, ai, env, ui/design-system, utils)
• The purpose is to host multiple deployable apps sharing code and infrastructure in one repository.
High-Level Architectural Components
a. Monorepo Shell
• Nx orchestrator, PNPM workspaces, Proto tool management
b. Applications
• Backend API (apps/backend)
• Frontend “Coursition” (Real-time editor/video player)
• Frontend “Legacy NMIT” (Next.js website/CMS)
c. Shared Libraries
• libs/api – API route definitions and HTTP clients
• libs/auth – Authentication logic and types
• libs/db – Prisma client & schema
• libs/env – Environment/secrets management (Infisical)
• libs/ai – AI utilities (document processing, media, generation)
• libs/utils – General utilities (media, date, string, subtitles)
• libs/ui/design-system – Shared React components/styles
d. External Services
• Relational database (Prisma / Supabase)
• Supabase config (apps/legacy_nmit/supabase)
• Stripe (payment via utils/stripe.ts)
• Liveblocks (real-time collaboration)
• Transcription/Media services
• CI/CD (GitHub Actions, zerops)
Interactions & Data Flows
• Frontends → Backend API via HTTP/REST (libs/api)
• Backend → Database via Prisma client (libs/db)
• Auth flows managed by libs/auth and NextAuth (legacy_nmit)
• Secrets injected at runtime via libs/env (Infisical)
• AI-driven features call libs/ai in backend or serverless functions
• Real-time editing uses Liveblocks in coursition frontend
• Payments routed from frontends/backends to Stripe via libs/utils/stripe.ts
• Assets and static content served from CDN or host (e.g., Next.js public/, coursition src/static)
Architectural Patterns & Principles
• Monorepo modularization by application and shared libraries
• Clear separation: UI apps, API layer, business logic (libs), data access (Prisma)
• Code reuse via Nx library boundaries
• Dependency inversion: frontends depend on shared libs, not on each other
• Environment-agnostic config with libs/env
• CI/CD configured per-app with GitHub workflows and zerops