How sagarkalyankar/tour-and-travel-packages works
Project Type and Purpose
• This is a full-stack “Tour and Travel Packages” application.
• Backend: Django project (Tour_Agency1/Tour_Agency + Yatraapp app) exposing REST endpoints, server-side templates, ORM models, admin interfaces, and static assets.
• Frontend: Angular single-page application under tour_agency/, consuming the backend’s APIs and serving client-side views for users and admins.
• Purpose: Allow end users to browse, book, and pay for tour packages; provide an admin dashboard to manage packages, bookings, and messages.
Main Components
a. Client Tier
• Angular SPA (tour_agency/src/app/* components & services)
• Browser running HTML/CSS/TS served from a web server or CDN (index.html, styles.css)
b. API Tier
• Django REST framework serializers and viewsets in Yatraapp/serializers.py & views.py
• URL routing via Tour_Agency/urls.py
• Authentication (login, register) and permission checks in Yatraapp/forms.py & DRF auth
c. Business Logic Tier
• Django ORM models (Yatraapp/models.py) for TourPackage, Booking, PaymentStatus, UserProfile, ContactMessage, etc.
• Services and forms for validations and workflows (forms.py)
d. Data Tier
• Relational database (PostgreSQL/MySQL/SQLite) storing migrations defined in migrations/
e. Admin Interfaces
• Django Admin (Yatraapp/admin.py) for admin-side CRUD
• Angular Admin components (src/app/admin/*) for a richer admin UI
f. Static & Media
• CSS, images under Yatraapp/static/ and Angular’s public/ folder
g. External Integrations
• Payment gateway (e.g., Stripe/PayPal) called from Angular or via Django views
• Email/SMS service for booking confirmations
h. Deployment & Infra
• Gunicorn/Uvicorn (WSGI/ASGI: wsgi.py, asgi.py) behind Nginx or Apache
• CI/CD pipelines (if applicable), containerization (Docker), hosting (AWS/GCP/Azure)
Relationships and Data Flow
• User’s browser → (HTTP/HTTPS) → Angular SPA
• Angular services (auth.service.ts, admin.service.ts) → (REST API calls) → Django endpoints
• Django endpoints → ORM → Database → ORM → Django → JSON → Angular
• Booking flow: Angular “BookPackageComponent” → POST /api/bookings/ → Django view → create Booking & Payment record → return status → Angular “PaymentComponent”
• Admin flow: Angular “AdminDashboardComponent” → GET /api/packages/ & /api/bookings/ → Django Admin APIs
• Static assets served by web server; media files (user uploads) possibly via S3 or local storage
Architectural Patterns & Principles
• Client-Server separation (SPA + REST)
• MVC on backend (Django’s Models, Views, Templates)
• Component-based UI on frontend (Angular modules & services)
• Layered architecture: Presentation (Angular, Django templates), Business logic (Django views/forms), Data access (Django ORM)
• DRY and Single Responsibility for each Angular component and Django app