How kanzariya-maulik/airbnb works
Project type and purpose
• This is a full-stack web application replicating core Airbnb features: user signup/login, listing creation, listing search, reviews, image upload, and map display.
File structure
• app.js: main Express application entry point
• init/: database seeding or startup scripts
• routes/: URL endpoints grouped by resource (listing, review, user)
• controllers/: business logic for each route
• models/: Mongoose schemas for listings, users, reviews
• utils/: custom error class and async wrapper middleware
• middelware.js: global middleware (authentication checks, flash messages)
• public/: static assets (CSS, JS, images, client-side map code)
• views/: EJS templates (layouts, partials, page views)
• cloudConfig.js: Cloudinary configuration
• Schema.js: Joi validation schemas
README for additional insights
• Backend stack: Node.js, Express.js, MongoDB/Mongoose
• Frontend stack: EJS templates, Bootstrap, custom CSS/JS
• Authentication: Passport.js (local strategy)
• Form validation: Joi
• External services: Mapbox for maps, Cloudinary for image upload
• Hosting: Render
Main components
a. Client Browser (Frontend)
• EJS-rendered pages
• Static assets: CSS, JS (map integration)
• Forms for signup/login, listing CRUD, review submission
b. Web Server (Backend – Express.js)
• Routing layer (routes/*.js)
• Middleware stack (middelware.js, wrapAsync, session, passport)
• Controllers (controllers/*.js)
• Validation layer (Joi schemas in Schema.js)
c. Data Layer
• MongoDB database
• Mongoose models (models/*.js)
• Init scripts to seed or configure
d. External Services
• Cloudinary (image storage/upload)
• Mapbox API (geolocation, map tiles)
e. Supporting Modules
• utils/ExpressError.js (error handling)
• utils/wrapAsync.js (async error wrapper)
Relationships and interactions
• Client → HTTP requests → Express routes
• Route handlers → call validation → controller logic
• Controllers → read/write → MongoDB via Mongoose
• Controllers → upload images → Cloudinary
• Views rendered server-side with dynamic data
• Client-side map scripts → call Mapbox API
• Passport.js → manages authentication flow (session cookies)
Architectural patterns and design principles
• MVC-like separation: Models, Controllers, Views
• Single-page form flows with server-side rendering
• Layered middleware for cross-cutting concerns (auth, validation, error handling)
• Modular routing for resource grouping
• Externalization of configuration (cloudConfig.js, .env)
Essential elements
• Session store/auth layer around Passport.js
• Static assets served from public/ directory