How prajwalwadekar/authify works
Project type and purpose
• Authify is a full-stack MERN (MongoDB, Express, React, Node.js) authentication system.
• It provides a complete user authentication flow: signup with email verification, login/logout, forgot/reset password, protected routes, and email notifications via Resend API.
File structure
Top level:
• backend/ – Express server
• frontend/ – React single‐page app
• outputs/ – screenshot assets
Backend substructure (MVC‐style):
• controllers/ – request handlers (auth.controller.js)
• routes/ – route definitions (auth.routes.js)
• models/ – Mongoose schemas (user.model.js)
• db/ – DB connection (connectDB.js)
• middleware/ – JWT verification (verifyToken.js)
• utils/ – token generation & cookie setting
• resend/ – email templates, service config
Frontend substructure:
• public/ – static assets, index.html
• src/
– components/ – reusable UI bits
– pages/ – route‐mapped views (Login, Signup, Dashboard, etc.)
– store/ – state management (authStore.js)
– utils/ – helper functions
• main.jsx & App.jsx – entry points
Config files: ESLint, Vite, package.json
README insights
• Describes features, tech stack, authentication flow steps, environment variables, and live demo.
• Emphasizes React+Tailwind UI, Express+JWT, MongoDB, Resend API.
Main components
a. Frontend (React SPA)
– Pages: Signup, Login, Dashboard, Email Verification, Forgot/Reset Password
– State store: authStore
– HTTP client (fetch/axios)
– Routing (React Router)
b. Backend (Node/Express API)
– Routes & Controllers: /api/auth
– Middleware: JWT verification
– Utils: token gen & cookies
c. Database
– MongoDB Atlas (User collection)
d. Email Service
– Resend API for sending verification & reset emails
e. External Clients & Environments
– Browser (client‐side)
– .env config (MONGO_URI, JWT_SECRET, CLIENT_URL, etc.)
Relationships & Interactions
1. User (Browser) → Frontend UI
2. Frontend → Backend API (HTTP requests to auth.routes)
• Signup: POST /signup → generate JWT, send email
• Email link callback: GET /verify-email?token=…
• Login: POST /login → set HTTP‐only cookie
• Forgot password: POST /forgot-password → send reset email
• Reset password: POST /reset-password → update DB
• Dashboard: GET /protected → JWT middleware
3. Backend ↔ MongoDB (CRUD on User)
4. Backend → Resend API (emailTemplates & emails)
Architectural patterns & design principles
• Client-Server separation (React client vs. Express server)
• MVC (Models, Controllers, Routes) on backend
• JWT-based stateless authentication with HTTP-only cookies
• Single‐Responsibility: separate modules for DB logic, email logic, token logic
• Environment abstraction (.env for secrets)