How nileshpandey05/wavechat works
Project type and purpose
• This is a full-stack, real-time chat application (“WaveChat”) organized as a Turborepo monorepo.
• It consists of three services in /apps (Next.js web client, Express HTTP API, ws-based WebSocket server), shared packages in /packages (Prisma DB client, shared types, auth utilities, UI components), and uses Docker/Docker Compose for deployment.
File structure
• Top-level directories:
• apps/http-server – Express.js REST API (authentication, user management, chat history REST endpoints)
• apps/ws-server – WebSocket server (real-time messaging)
• apps/web – Next.js frontend (pages, components, chat UI)
• packages/db – Prisma schema + migrations + generated client
• packages/backend-common – shared server logic (JWT handling, configuration)
• packages/common – shared TypeScript interfaces/types
• packages/ui – shared React UI primitives
• Configuration files: docker-related files, Turborepo config (turbo.json), TS configs, GitHub Actions workflows
README for additional insights
• Tech stack: Express.js + ws for backend, PostgreSQL + Prisma ORM, JWT + bcrypt for auth, Next.js + Tailwind + shadcn/UI for frontend
• CI/CD with GitHub Actions, container orchestration with Docker Compose