How event-ticketing-devs/event-ticketing-platform works
Project type and purpose
• This is a full-stack event ticketing and management platform.
• Frontend built with React and Vite; backend with Node.js, Express, MongoDB and Redis.
• Purpose: let attendees browse and book events, organizers manage events and contacts, admins oversee the system.
File structure
• Top-level: folders “backend” and “frontend.”
• backend/src contains:
• app.js and server.js for Express setup and entry point
• controllers (auth, booking, category, contact, event, payment, report, user)
• models for MongoDB schemas (User, Event, Booking, Category, Contact, Report)
• routes mapping HTTP endpoints to controllers
• middleware for authentication, rate limiting, error handling, roles
• utils (mailer, QR code generator, Cloudinary, refund logic)
• redis client and helpers for caching and rate limits
• constants and environment-based configuration
• frontend/src contains:
• main.jsx and App.jsx
• pages directory for route-based pages (Home, Events, BookingFlow, AdminDashboard, OrganizerDashboard, Profile, etc.)
• components directory for reusable UI pieces (Navbar, Footer, QRScanner, StripeCheckout, modals, route guards)
• api client wrapper and services for HTTP calls (authService, apiClient)
• context for global state (AuthContext)
• utilities for route protection and tests
• Configuration files: package.json, tsconfig/vite.config, ESLint rules.
README for additional insights
• Tech stack: React, TailwindCSS, Axios, React Router, Node.js, Express, Mongoose, Redis, Stripe, Google OAuth, Cloudinary.
• Key features: role-based auth, Google OAuth, Stripe payments, QR code tickets, contact management, rate limiting, refund policy.
• Contains API endpoints by resource and method.
• Describes environment variables and external integrations (MongoDB URI, Redis, Stripe keys, Google Maps, Cloudinary).
Elements
• API server modules in another (green).
• Data stores in a third (orange).
• External services in gray.
Detail without over-thinking
• Every major folder or integration in your file tree has a corresponding block.
• Middleware chain and where rate limiting and error handling plug in.
• Flow of booking from search → payment → QR generation → verification.
• Role-based routes: public vs. admin vs. organizer.
• Timeouts or caching strategies (Redis TTL for rate limits).