How sonali2109/capital works
Project type and purpose
• This is a full-stack, monorepo-based event ticketing platform (“Capital”).
• Frontend: Next.js (apps/web) delivering pages/routes and UI components.
• Backend: Node HTTP service (apps/http) exposing RESTful endpoints.
• Shared packages: database layer, cache, notification service, types, UI primitives, lint/TS configs.
• Infrastructure: Docker-Compose for orchestrating HTTP, Web, Postgres, Redis, etc.
File structure
• Top-level “apps/” folder splits into:
• apps/http – the standalone Node service (src/app.ts, routes/*.ts, server.ts)
• apps/web – Next.js app leveraging app/ router, client/server components, API routes
• “packages/” contains discrete libraries:
• packages/db – Prisma schema, migrations, seed scripts
• packages/cache – Redis caching wrappers
• packages/notifications – email templating & dispatch
• packages/types – shared TypeScript interfaces
• packages/ui – design system primitives for React
• lint/config tooling
• Dev tooling: turbo.json (monorepo task runner), Dockerfiles, docker-compose.yml
README for additional insights
• Purpose: Secure, cryptographically tamper-proof tickets, account-bound, real-time validation