How 8bit-parth/atlas-go works
Project Type and Purpose
• This is a full-stack web application built with Next.js (v13+ App Router).
• It delivers a dynamic property‐listing site: users can browse, create, favorite, and reserve listings on an interactive map.
• It uses Prisma (via app/lib/db.ts) to access a Postgres database (defined in prisma/schema.prisma), Supabase (via app/lib/supabase.ts) for storage/auth extensions, and KindeAuth (via API routes) for authentication.
File Structure Analysis
• Top‐Level
• Dockerfile & docker-compose.yml: containerization of Next.js server and Postgres.
• next.config.mjs, tsconfig.json, tailwind.config.ts, postcss.config.js: build and styling configs.
• prisma/: database schema.
• public/: static assets.
• “app/” (Next.js App Router)
• app/page.tsx, app/layout.tsx: root page and layout.
• app/components/: React UI components for map, listing cards, filters, nav.
• app/api/: serverless routes for auth (KindeAuth) and user‐creation flows.
• app/create/, app/home/, app/favorites/, app/my-homes/, app/reservations/: segmented pages for different user flows.
• app/lib/: wrappers for DB (Prisma), Supabase, utility functions (countries, categories).
• “components/ui/”: reusable design‐system primitives (buttons, inputs, cards) likely built with Tailwind.
• package.json: Next.js, React, Prisma, Supabase, KindeAuth, Tailwind, map‐related libs.
Key Architectural Patterns
• Hybrid CSR/SSR with React Server Components (Next.js App Router).
• Router-based code splitting: each route (e.g., /create/[id]/address) is its own server component + client components.
• API layer inside Next.js (app/api/*) acting as microservice‐style endpoints.
• ORM (Prisma) abstracts Postgres.
• External services: KindeAuth for authentication, Supabase for storage/real-time features, Map API for geospatial.
a. Main Components
• Browser (User) – renders React UI, calls RESTful API routes.
• Next.js Server
– Server Components & Client Components
– API Routes (KindeAuth handlers, user-resource endpoints)
• Database (Postgres via Prisma)
• Supabase Service (storage, real-time, optional auth)
• External Auth Service (KindeAuth)
• API (e.g., Google Maps)
b. Data Flows
1. User browses UI → Next.js SSR/CSR renders pages.
2. UI triggers actions (e.g., login, create listing) → calls Next.js API route.
3. API route invokes KindeAuth or Supabase SDK, or Prisma client.
4. Prisma performs SQL on Postgres.
5. Supabase handles file storage or real-time subscriptions.
6. Components fetch tile/geo-data from Map API.
c. Architectural Patterns
• MVC‐style separation:
– View: React components (app/components & components/ui)
– Controller/Service: Next.js API routes & server components
– Model: Prisma models (prisma/schema.prisma)
• Microfrontend‐like routes: each feature (create, reservations, favorites) isolated in its own folder.
d. Technologies
• Next.js (SSR/SSG, App Router)
• React 18+ (Server & Client components)
• Prisma ORM + Postgres
• Supabase SDK
• KindeAuth SDK
• Tailwind CSS
• Docker & Docker Compose