How noob-master-cell/esn works
Project type and purpose
• This is a full-stack event management platform (“ESN Event Management Platform”).
• Frontend is a React/TypeScript single-page application (Vite + Apollo Client).
• Backend is a monolithic GraphQL API built with NestJS, Prisma (PostgreSQL), Redis, and Auth0 for authentication.
• Docker-based development and deployment with docker-compose for PostgreSQL, Redis, backend, and frontend containers.
File structure
• Top-level folders:
• backend – NestJS GraphQL server, Prisma schema & migrations, custom scripts, PM2/Ecosystem config, load-test definitions.
• frontend – React (TSX) app organized by pages, components, hooks, GraphQL queries, Vite config, Tailwind/CSS, Dockerfile.
• docs – markdown docs for API, DB, dev workflow, deployment, maintenance.
• docker-compose*.yml – defines multi-container development and prod stacks.
• scripts – shell scripts for deployment, health checks, docker builds.
• Patterns & configurations:
• NestJS modules by feature (auth, users, events, comments, feedback, etc.).
• GraphQL resolvers → services → Prisma ORM → PostgreSQL.
• Redis used for caching, rate-limiting (throttler), and pub/sub (realtime comments/feedback).
• Auth0 guard + role guard for RBAC.
• Cloudinary integration for image uploads.
README for additional insights
• Confirms GraphQL API, Redis caching, rate limiting, role-based access control, Auth0.
• Highlights Docker-based local dev and production deployment.
• Docs folder references architecture-relevant info (DATABASE.md, DEPLOYMENT.md).
Elements
• Clear rectangular blocks for each component (e.g., “React SPA”, “NestJS GraphQL Server”, “PostgreSQL”, “Redis”, “Auth0”, “Cloudinary”).
• Green = User-facing (Frontend)
• Blue = Application logic (Backend GraphQL)
• Orange = Data stores (DB, Cache)
• Gray = External services