How ishu077/course_project_bnb works
Project type and purpose
• WanderLust is a full-stack MVC web application for booking BnB stays (“Airbnb-like”)
• Key capabilities: user signup/login, CRUD listings & reviews, map display, cloud image upload
File structure
• app.js: Express application entrypoint
• cloudConfig.js: Cloudinary configuration
• init/: database seeding
• Models/: Mongoose models (User, Listing, Review)
• controllers/: business logic for listings, reviews, users
• routes/: Express route definitions
• middleware.js: auth checks, error handling
• utils/: error classes, async wrapper
• schema.js: JOI validation schemas
• public/: static assets (CSS, JS, client-side scripts)
• views/: EJS templates (layouts, partials, pages)
• uploads/: temporary file storage for Multer
README for stack and features
• Frontend: EJS, Bootstrap, custom CSS/JS, Mapbox integration
• Backend: Node.js + Express, MongoDB + Mongoose, Passport.js, Multer, Cloudinary
• External services: Cloudinary for images, Mapbox for maps
Main components and their interactions
A. Client (Browser)
• Sends HTTP requests (GET, POST, PUT, DELETE)
• Renders HTML from EJS, executes client-side JS (map.js, script.js)
B. CDN / Static Server
• public/ served via Express.static
• Assets: CSS, JS, images (mapbox scripts)
C. Express Server
• app.js sets up middleware (session, passport, flash, body-parser, multer)
• Routes → Controllers → Models/Services
D. Controllers & Services
• controllers/**: orchestrate CRUD flows
• schema.js + middleware.js validate and sanitize input
• utils/wrapAsync and expressError enforce uniform error handling
E. Data Layer
• Mongoose models under Models/
• MongoDB Atlas (DB_URL) stores users, listings, reviews
F. External Services
• Cloudinary: image upload via multer-storage (cloudConfig.js)
• Mapbox: geocoding/maps in client JS
G. Init Module (optional)
• init/index.js seeds test data
Architectural patterns & design principles
• MVC pattern: Routes → Controllers → Models → Views
• Layered architecture:
• Presentation (EJS + static assets)
• Application (Express middleware + controllers)
• Persistence (Mongoose → MongoDB)
• Integration (Cloudinary, Mapbox)
• Single monolithic service (no microservices), but clear separation by folder
Details
• Authentication flow: User → Passport → Session store
• File upload flow: Browser → Multer → Cloudinary → DB (image URL)
• Validation: Routes → JOI schema → Controllers
• Error handling: Controllers → expressError middleware → Error view