How jumyeong33/wodmon works
Project type and purpose
• This is a NestJS–Prisma backend service (Node.js + TypeScript) implementing REST HTTP endpoints for user management, authentication (JWT + Google OAuth), and workout-of-the-day (WOD) resources (hero-wod, wods, tags).
• It exposes JSON APIs consumed by clients (web/mobile), persists data in a relational database via Prisma ORM, and integrates with Google OAuth for social login.
File structure
• Top-level:
• src/app.module.ts – root module binding all features
• src/main.ts – application bootstrap (NestFactory)
• src/auth, src/users, src/hero-wod, src/wods, src/tags – feature modules (controllers, services, DTOs, Prisma schemas)
• src/prisma – PrismaModule and PrismaService (DB connection, injection)
• src/common, src/utils – cross-cutting concerns (guards, decorators, filters)
• prisma/schema.prisma and prisma/migrations – database schema definitions and migration history
• Configuration: nest-cli.json, tsconfig.json, package.json, Docker or CI config can be added if needed.
README for additional insights
• Lists commands to start in dev/prod, run tests, generate migrations.
• Technology stack: Node.js, NestJS, Prisma, Jest for tests.
Detailed elements
• Service layer: note business logic classes in each module
• PrismaService: show as a shared component imported by all modules requiring DB access