How vivek0409-7/maharashtra-tour works
Aagman is a Maharashtra tourism portal combining destination discovery with account access and itinerary planning. The main planning flow is: a visitor submits trip preferences in the frontend, which calls the planner API; the controller requests a Gemini itinerary and saves it as a journey, while visitors can retrieve saved journeys. The portal also provides separate destination-browsing areas for forts and hills, temples, beaches, and heritage sites. Backend excerpts show route dispatch and model usage; destination links and frontend page wiring are not fully sampled, so those relationships are not inferred.
Main entry points: plannerRoutes.js Planner routes · server.js Express API server · script.js Planner and sessions · plannerController.js Itinerary controller
Components 18
Destination discovery
- Tourism portal
frontend/index.html - Forts and hills
frontend/branch1/Ginfo/branchscript.js - Temple destinations
frontend/branch2/temples - Beach destinations
frontend/branch3/beaches/script.js - Heritage sites
frontend/branch4/sites
Journey planning
- Planner and sessions
frontend/script.js - Planner routes
backend/routes/plannerRoutes.js - Itinerary controller
backend/controllers/plannerController.js - Journey model
backend/models/Journey.js
Accounts
- Account interface
frontend/script.js - Account routes
backend/routes/authRoutes.js - Account controller
backend/controllers/authController.js - User model
backend/models/User.js
API and persistence
- Express API server
backend/server.js - Database connection
backend/config/db.js
Other components
- Visitor
- Gemini AI
- In-memory MongoDB
Connections 15
- Visitor → Tourism portal: browses
- Visitor → Planner and sessions: submits preferences
frontend/script.js - Planner and sessions → Planner routes: posts itinerary request
frontend/script.js - Planner and sessions → Planner routes: fetches saved journeys
frontend/script.js - Planner routes → Itinerary controller: dispatches to
backend/routes/plannerRoutes.js - Itinerary controller → Gemini AI: requests itinerary
backend/controllers/plannerController.js - Itinerary controller → Journey model: saves and queries
backend/controllers/plannerController.js - Visitor → Account interface: uses account forms
frontend/script.js - Account interface → Account routes: calls auth endpoints
frontend/script.js - Account routes → Account controller: dispatches to
backend/routes/authRoutes.js - Account controller → User model: reads and saves users
backend/controllers/authController.js - Express API server → Database connection: connects database
backend/server.js - Express API server → Account routes: mounts routes
backend/server.js - Express API server → Planner routes: mounts routes
backend/server.js - Database connection → In-memory MongoDB: starts instance
backend/config/db.js