How bsk03/live-feedback-wall works
Project type and purpose
• This is a full-stack web application scaffolded with the T3 Stack (Next.js App Router, NextAuth, Drizzle ORM, Tailwind CSS, tRPC).
• From the file tree and README, we see a real-time “rooms/chat” feature, a panel for room management, authentication pages, database migrations under drizzle/, and Docker scripts.
File structure
• Top-level:
• docker-compose.yml + start-database.sh: orchestrate your database (e.g., PostgreSQL) in Docker.
• drizzle/ folder: SQL migrations and snapshots.
• server.js / server.mts: entrypoints for socket server or custom API server.
• next.config.js, tsconfig.json, lint/format configs.
• Source directories under src/:
• src/app/: Next.js App Router—React pages, layouts, and serverless API routes at src/app/api/.
• src/components/: React UI components (landing pages, auth flows, panel, rooms, QR generator).
• src/hooks/: custom React hooks (infinite scroll, socket room).
• src/lib/: client & server utilities (socketClient, auth-client, server-only).
• src/server/: tRPC routers and database schema using Drizzle.
• src/store/: Zustand or similar for client state (authStore).
• src/trpc/: tRPC client/server setup.
• public/: static assets.
README for additional insights
• Confirms tech stack: Next.js, NextAuth.js, Drizzle (ORM), Tailwind, tRPC.
• Mentions deployment via Docker, Vercel, Netlify.
Essential details to capture
• Next.js App Router structure (pages & API routes)
• tRPC client/server boundary
• Authentication flow (NextAuth endpoints, session validation)
• Real-time channel (Socket.io pipeline)
• Database migrations & schema (Drizzle)
• Docker-based DB in local/dev vs. production