How saurabh7431/trendmart works
Project type and purpose
• TrendMart is a monolithic full-stack e-commerce web application built on Node.js and Express.js.
• It uses MVC (Model-View-Controller) architecture, with EJS templates for server-side rendering and Tailwind CSS for styling.
• Key features: user authentication (both admin and regular users), product management, shopping cart, order processing, image uploads, and payment integration (Razorpay).
File structure
• Top-level:
• app.js – Express app setup, middleware registration, route mounting.
• config/ – environment configuration (DB connections, Multer, API keys).
• controllers/ – business logic (auth, product, cart, order).
• routes/ – Express routers for each resource (home, cart, user, owner/admin, products).
• models/ – Mongoose schemas (User, Owner, Product, Order).
• middleware/ – auth guards (isLoggedIn, isAdminLoggedIn).
• views/ – EJS templates (UI pages, partials).
• public/ – static assets (images, CSS).
• uploads/ – user-uploaded images.
• utils/ – helper functions (JWT token generation).
• config/mongoose-connection.js – establishes MongoDB connection.
• vercel.json – deployment config.
• postcss.config.js & tailwind.config.js – CSS build.
Main components
a. Client (Browser)
b. Express.js Server (monolithic)
• Route Handlers
• Middleware Layer
• Controllers (auth, product, cart, order)
• Utility Layer (JWT generation, file upload config)
• View Engine (EJS templates)
• Static file server (public folder)
c. Database (MongoDB via Mongoose)
d. File Storage (local uploads folder, managed by Multer)
e. External Payment Service (Razorpay)
Relationships and interactions
• Client → Server: HTTP(S) requests for pages, API calls, form submissions
• Server Middleware → Controllers → Database (CRUD via Mongoose)
• Controllers → View Engine: render EJS with dynamic data
• Controllers → Static Assets: serve CSS/JS/images from “public”
• Controllers → File Storage: Multer handles image uploads to “uploads/”
• Controllers → External Payment Service: initiate payment, receive callbacks
Architectural patterns & design principles
• MVC pattern: clear separation of Models (models/), Views (views/), Controllers (controllers/)
• Layered architecture: routing → middleware → business logic → data access
• Single codebase monolith: all modules packaged in one deployment unit
• Environment-based config in config/ (12-factor style)
Technologies & frameworks
• Node.js, Express.js (web framework)
• MongoDB with Mongoose (ODM)
• EJS (template engine)
• Tailwind CSS & PostCSS (styling)
• Multer (multipart form‐data uploads)
• JWT (authentication tokens via utils/)
• Razorpay (payment gateway integration)
• Vercel (hosting, as per vercel.json)