shijuvtm/meetup

Purpose and Deployment Shape

This is a containerized meetup/event RSVP tracker. A Next.js frontend calls an Express API, which persists users, events, and RSVP state in PostgreSQL/Neon. Docker Compose orchestrates frontend and backend containers via docker-compose.yml; backend startup and database setup are defined in backend/Dockerfile, backend/entrypoint.sh, and backend/init-db.js.

Backend API Entry and Composition

The Node process starts at backend/server.js, which loads the Express application from backend/src/app.js. The app composes API routes and shared middleware, separating HTTP wiring from domain handling. Backend dependencies and runtime scripts are declared in backend/package.json.

Authentication Boundary

Authentication is exposed through backend/src/routes/authRoutes.js and implemented in backend/src/controllers/authController.js. It uses bcrypt password hashing and JWT issuance. Protected requests cross the authorization boundary in backend/src/middleware/auth.js, which validates tokens and supplies authenticated identity for ownership-guarded event actions.

Event and RSVP Domain

Event lifecycle and RSVP operations are routed through backend/src/routes/eventRoutes.js and handled in backend/src/controllers/eventController.js. This layer owns creation, editing, deletion, retrieval/filtering, and RSVP status changes. Event mutation authorization depends on the authenticated user established by the auth middleware.

Persistence and Database Lifecycle

PostgreSQL access is centralized in backend/src/config/db.js, using the DATABASE_URL connection to a Neon-hosted database. The relational schema is defined in backend/schema.sql; initialization and optional initial data paths are backend/init-db.js and backend/seed.js. The database is an external managed service rather than a local Compose service.

Frontend Application and Client State

The Next.js application is rooted at frontend/app/layout.tsx and frontend/app/page.tsx. Authentication state is shared through frontend/context/AuthContext.tsx, while API requests are centralized in frontend/lib/api.ts, using the public backend URL environment variable. frontend/components/Navbar.tsx is the cross-page navigation/auth-facing UI boundary.

User Flows and Pages

The frontend maps event operations to App Router pages: event detail at frontend/app/events/[id]/page.tsx, event editing at frontend/app/events/[id]/edit/page.tsx, and creation at frontend/app/events/create/page.tsx. Login begins at frontend/app/login/page.tsx. These pages read/write through the API client; the backend enforces JWT identity and event ownership rather than trusting client state.