ruthwik2/event-media-platform

Purpose and Runtime Topology

A full-stack event-photography platform: events contain albums, albums contain photo/video media; users discover, share, moderate, and engage with content. It runs as a Next.js frontend, Express API/Socket.IO server, and PostgreSQL database, containerized together via docker-compose.yml. Core backend entry point: backend/src/app.js; frontend App Router root: frontend/src/app/layout.tsx.

Web Client and Navigation

The Next.js 14 client separates unauthenticated and protected experiences through route groups, with a shared main layout/navigation. Major workflows include gallery/search, media detail, uploads, event/album management, sharing, profiles, notifications, and admin approval queues.

Paths: frontend/src/app/(auth)/layout.tsx, frontend/src/app/(main)/layout.tsx, frontend/src/app/(main)/events/[id]/page.tsx.

API Composition and Authorization Boundary

Express mounts resource routers below /api for auth, events, albums, media, notifications, and club settings. Controllers implement resource workflows; JWT middleware authenticates requests and enforces role/access rules. Roles include admin, photographer, club member, and viewer, with additional private-content and collaborator/access-request controls.

Paths: backend/src/app.js, backend/src/middleware/auth.js, backend/src/routes/mediaRoutes.js.

Persistent Domain Model

Prisma/PostgreSQL is the source of truth for users, events, albums, media, social interactions, tags, notifications, access requests, and club settings. The central hierarchy is Event → Album → Media; media also connects to face metadata, AI labels/captions, moderation state, and user interactions. Schema migrations evolve approval, sharing, privacy, tag positioning, categories, and moderation.

Paths: backend/prisma/schema.prisma, backend/prisma/migrations/20260602000000_add_access_requests/migration.sql, backend/prisma/seed.js.

Media Ingestion and Delivery Pipeline

Bulk uploads enter through Multer middleware, then media controllers coordinate persistence and derived processing. sharp creates thumbnails/compressed output and composites SVG watermarks for downloads. Storage is a deployment boundary: local disk by default or AWS S3 when enabled. Media capabilities include search, favourites, tagging, comments, likes, download tracking, and visibility-aware delivery.

Paths: backend/src/middleware/upload.js, backend/src/controllers/mediaController.js, backend/src/services/imageService.js.

AWS Intelligence Pipeline

When S3/AWS are configured, uploaded images are analyzed through Rekognition for face indexing/search, labels, automatic captions, and content moderation. A user selfie establishes a Rekognition face identity; “My Photos” queries matching indexed media. Without S3/AWS credentials, this enrichment path is intentionally skipped rather than emulated.

Paths: backend/src/services/rekognitionService.js, backend/src/services/s3Service.js, backend/src/config/aws.js.

Sharing, Notifications, and Realtime

Events and albums expose guest-access paths via QR codes and share tokens, separate from authenticated API access. Tags, likes, comments, and approvals create notifications, delivered live through Socket.IO and represented in frontend Zustand state. The client establishes its realtime connection through a dedicated hook.

Paths: backend/src/services/notificationService.js, backend/src/config/socket.js, frontend/src/hooks/useSocket.tsx.

Deployment and External Dependencies

Docker orchestration provisions Postgres, backend, and frontend; backend configuration covers database, AWS, sockets, and logging. Browser API access is through the Axios client, while API CORS and Socket.IO depend on frontend/backend URLs. Material external services are PostgreSQL, optional AWS S3, and AWS Rekognition.

Paths: docker-compose.yml, backend/src/config/database.js, frontend/src/lib/axios.ts.