How angaddogra/wandermate-your-travel-companion works
Project Type and Purpose
• Full-stack web application built on Django (Python).
• Purpose: AI-powered itinerary generation (“WanderMate”).
Main Components
a. Client (Web Browser)
b. Django Web Server
– URL Dispatcher (plannerproject/urls.py & globe/urls.py)
– Views & Business Logic (globe/views.py)
– Templates (globe/templates/globe/*.html)
– Models & ORM (globe/models.py → db.sqlite3)
c. Database
– SQLite (db.sqlite3)
d. External AI Service
– (e.g., OpenAI or another NLP/ML API called from views)
e. Static/Media File Handler (if any)
f. Optional Production Layer
– WSGI/ASGI (plannerproject/wsgi.py, asgi.py)
– Reverse Proxy (e.g., Nginx/Gunicorn)
Relationships & Data Flow
• Browser → HTTP Request → Django URL Dispatcher
• Dispatcher → Invokes View Function
• View:
– Validates Input / Session / Auth (globe/login, signup)
– Reads/Writes Models via ORM → SQLite
– Calls External AI API to generate itineraries
– Renders Template with Data → HTML Response
• Response → Browser
• (In Prod) WSGI/ASGI Layer connects web server to Django app
Architectural Patterns & Principles
• MVT (Model-View-Template) – separation of concerns
• Single Django app (“globe”) under one project – monolithic
• ORM abstracts data layer (db.sqlite3 migration files)
• External service integration for AI functionality
• Clearly defined URL→View→Template pipeline
Essential Elements
• Component labels (e.g., “Client,” “Django URL Dispatcher,” “SQLite DB”).