How krishsavaliya/wanderlust-airbnb-clone- works
Project type and purpose
• This is a full-stack web application ("Wanderlust") inspired by Airbnb.
• It implements user authentication, listing CRUD, image uploads, map integration, geocoding, and reviews.
File structure
• Top-level files:
• app.js (Express server entry point)
• Schema.js, cloudConfig.js (DB schema and cloudinary setup)
• init/ (database seeding scripts)
• package.json (dependencies and scripts)
• Directories:
• controllers/ – Express controller logic for listings, reviews, users
• routes/ – Route definitions binding URLs to controllers
• models/ – Mongoose schemas for Listing, Review, User
• views/ – EJS templates (layouts, partials, pages)
• public/ – Static assets (CSS, JS, images)
• utiles/ – Custom middleware and error helpers
• middleware.js – global Express middleware (validation, auth checks)
README for additional insights
• Technology stack: Node, Express, MongoDB, Mongoose, Passport.js, Cloudinary, Multer, Joi, express-session, connect-flash, EJS, Bootstrap, MapLibre GL JS, Geoapify
• Features: authentication, file upload, mapping, geocoding, responsive UI
Main components and their relationships
a. Client/browser UI
• Static assets (CSS/JS/images) served from public/
• EJS templates rendered server-side
• Interactive map widget calling MapLibre + Geoapify APIs
b. Web server (Express)
• Entry point: app.js
• Middleware chain: session, flash, body-parser, cloudinary config, custom middleware.js
• Routes layer: routes/*.js delegates to controller functions
• Controllers: business logic for listings, reviews, users
• File upload handling: Multer + Cloudinary SDK
• Form validation: Joi schemas in middleware
• Authentication: Passport-local strategy, express-session, connect-flash
c. Data layer
• Models (Mongoose schemas) for Users, Listings, Reviews
• MongoDB (hosted or local)
• init scripts to seed initial data
d. External services
• Cloudinary API for image storage
• Geoapify API for geocoding
• (Implicit) MapLibre GL JS for client-side map rendering
Architectural patterns and principles
• MVC: Views (EJS) ←→ Controllers ←→ Models (Mongoose)
• Layered architecture:
• Presentation layer (EJS + public JS/CSS)
• Application layer (Express routes/controllers)
• Domain/data layer (Mongoose + MongoDB)
• Separation of concerns: routing, business logic, data access, validation, error handling
• External abstraction: middleware for auth, file uploads, error wrapping (wrapAsync)
Relationships and data flows
• From Client → Express (HTTP requests for pages, API calls)
• Express → Middleware → Controllers → MongoDB (CRUD)
• Controllers → Cloudinary API (upload images)
• Controllers → Geoapify API (get coordinates)
• MongoDB → Controllers → EJS views → Client (rendered HTML)