How ezeibekweemma/google-drive-clone works
Project Type and Purpose
• This is a full-stack, cloud-storage web application (“Google Drive Clone”) built with Next.js (React + TypeScript).
• It provides user authentication (NextAuth.js), file upload/management, search, and folder navigation, backed by Firebase (Firestore + Storage) and a relational database accessed via Prisma.
File-Structure Analysis
Top-level directories:
• prisma/ – your schema.prisma defines your relational DB tables (users, sessions, etc.).
• public/ – static assets (logo, screenshots).
• src/
– components/ – React UI components (Navbar, FileHeader, SideMenu, etc.).
– pages/ – Next.js pages and API routes (auth routes, drive views, serverless functions).
– API/ – client-side wrappers for Firestore and file-upload operations.
– server/ – server-side utilities: db.ts (Prisma client), auth.ts (NextAuth adapter setup).
– hooks/ – custom React hooks for data fetching.
– firebaseConfig.tsx – Firebase SDK initialization.
Config files: next.config.mjs, tsconfig.json, ESLint, Prettier, Tailwind config.
Key Insights from the README
• NextAuth.js for authentication
• Firebase (Firestore + Storage) for data and files
• Prisma managing relational data (likely for NextAuth adapters and any server-side metadata)
• Deployed on Vercel
Main Components & Interactions
A. Frontend (Next.js + React)
• Pages render via SSR/SSG, and client-side navigation (drive views, file/folder UI).
• Components communicate with backend API routes and directly with Firebase SDK for file operations.
B. Authentication Layer (NextAuth.js)
• pages/api/auth/[...nextauth].ts implements authentication providers.
• Uses Prisma adapter (src/server/db.ts) to persist user/session data in relational DB.
C. Backend API (Next.js Serverless Functions)
• pages/api routes for any custom server logic (e.g., additional folder or file metadata management).
• src/server/db.ts provides a Prisma client to these functions.
D. Databases & Storage
1. Relational DB (Postgres/SQLite) via Prisma – stores user accounts, sessions, metadata.
2. Firebase Firestore – stores file/folder metadata in a NoSQL store.
3. Firebase Storage – stores binary file contents.
E. Hosting & Deployment
• Vercel hosts the Next.js application (frontend + serverless API).
• Firebase is a third-party managed service for storage and real-time database.
Architectural Patterns & Principles
• Full-stack separation: clear distinction between UI, API, and data layers.
• Serverless functions for on-demand backend operations (Next.js API routes).
• Adapter pattern: NextAuth.js uses a Prisma adapter for DB interactions.
• Client-SDK usage for Firebase to reduce server load on file uploads/downloads.
• Hooks and reusable components on the front end to maintain modularity.
1. “User Browser” – React/Next.js SPA & SSR pages
2. “Next.js Serverless API” – pages/api routes + NextAuth endpoints
3. “Prisma PostgreSQL DB” – relational store for users, sessions, metadata
4. “Firebase Firestore” – NoSQL store for file/folder metadata
5. “Firebase Storage” – blob storage for actual files
7. “NextAuth.js” – authentication service layer (can be grouped inside API)
• Browser → Next.js pages (SSR/SSG)
• Browser → Next.js API (REST calls for metadata operations)
• Next.js API → Prisma DB (CRUD for user & session data)
• Browser (Firebase SDK) → Firestore (read/write file metadata)
• Browser (Firebase SDK) → Firebase Storage (upload/download blobs)
• NextAuth.js internal calls from API → Prisma DB
c. Technologies & Frameworks
• NextAuth.js as the auth provider.
d. Architectural Patterns
• “Serverless / API Routes” within Next.js
• “Prisma Client” inside the API container
• Client SDK bypassing your server for file transfers