How aashutoshrathi/medtour works
Main System Components
a) Web Application Layer
• Django Framework as the core
• Three main Django apps:
• Landing App (User Management & Authentication)
• Hospital App (Medical Services Management)
• MedTour Core (Project Configuration)
b) Database Layer
• Based on Django's presence, likely PostgreSQL (for Heroku deployment)
• Major data models
c) External Services
• Email Service (evident from email templates)
• Static File Hosting (for CSS/JS/images)
Detailed Component Breakdown
Frontend Components:
• Base template (landing/templates/landing/base.html)
• User-specific views (patient_home, doc_home)
• Hospital management views
• Authentication views
Backend Components:
• Authentication System
• Custom user management (visible in landing app)
• Social authentication (pipeline.py suggests this)
• Hospital Management System
• Appointment handling
• Doctor profiles
• Hospital profiles
• Location Services
• Region and City management
Data Flow Representation
• User request flow through URLs (medtour/urls.py → app-specific urls.py)
• Form submissions (landing/forms.py, hospital/forms.py)
• Authentication flow
• Appointment booking process
Specific Architectural Elements
[Client Browser] ←→ [Django Web Server]
• ↑ ↑
• [Static Files] [Database]
• ↑ ↑
• [File Storage] [Email Service]
Important Details
• User Types (Patients, Doctors, Administrators)
• Authentication flows
• Appointment management system
• Hospital and doctor profile management
• Location-based services
• Static file handling (CSS/JS/images)
Technical Stack Indicators
Technologies:
• Django Framework
• UIKit (frontend framework, evident from static files)
• Service Worker (for progressive web app features)
• Database system
• Email service integration
Deployment Architecture
Include:
• Heroku hosting environment
• Static file serving
• Database service
• Web server configuration