How lexiesm/dccommit works
Project type and purpose
• This is a full-stack social/community web application.
• Frontend: Next.js 13 (app router) + React + Clerk for auth.
• Backend: Node.js/TypeScript Express REST API using Prisma ORM (PostgreSQL) and Supabase.
• Use cases: user registration & authentication, creating posts, comments, reporting content, admin/moderator dashboards.
File structure
• Top-level “front” directory: a Next.js project with:
• src/app – React pages & layouts.
• src/components – reusable UI components.
• src/services – client-side wrappers around backend HTTP calls.
• Clerk config (.clerk), middleware, and Next config.
• Top-level “back” directory: an Express/TypeScript REST API:
• src/api/controllers & src/api/routes – MVC-style controllers & route definitions.
• lib/prisma.ts – Prisma client setup.
• prisma/schema.prisma & prisma/migrations – database schema + migrations.
• supabase/ – Supabase config (storage, functions).
• generated/prisma – compiled Prisma client.
• Common configuration: tsconfig.json, eslint.config, package.json in each.
Main components
A. Client (Browser)
• Next.js SSR & CSR pages
• React components
• services/*.ts – HTTP clients to the API
B. API Gateway / Auth Layer
• Clerk authentication middleware (both front & back)
• Next.js middleware and back/src/api/auth-clerk
C. Backend REST API
• Express app.ts → routes → controllers
• Business logic layer (controllers → lib services if any)
• Prisma client for DB operations
• Supabase SDK for storage or real-time functions
D. Database
• PostgreSQL (managed via Prisma Migrations)
• Schema defined in prisma/schema.prisma
E. External Services
• Clerk (authentication, user management)
• Supabase (file storage, edge functions)
• Postman (for API testing – not shown in runtime)
Relationships & data flow
• Browser → Next.js server (SSR/ISR)
• Calls internal pages or fetches client services →
• services/*.ts invoke API endpoints (e.g., GET /posts, POST /comments)
• Next.js middleware uses Clerk to validate tokens/cookies
• Browser direct calls to Clerk for sign-in/out (if applicable)
• REST API receives requests → Clerk middleware → route handlers → Prisma & Supabase → responses
• REST API → Database via Prisma
• REST API → Supabase Storage (e.g., image uploads)
Architectural patterns & design principles
• Layered architecture: Presentation (front), API (controllers), Data (Prisma/DB).
• MVC-style controllers with explicit routing.
• Separation of concerns: Next.js for UI and SEO; Express for business logic.
• Infrastructure as code: Prisma schema & migrations.
• External auth offloading to Clerk; file handling via Supabase.
Technologies / frameworks
• Frontend: Next.js 13 App Router, React, TypeScript, Clerk SDK, CSS modules.
• Backend: Node.js, Express, TypeScript, Prisma ORM, Supabase JS.
• Database: PostgreSQL.
• Testing/Triage: Postman collection (API DCCommits.postman_collection.json).