How eldardautovic/ridewithme works
Main Components Identification
The system consists of several key components:
• Frontend Applications (Flutter-based)
• Admin Panel (ridewithme_admin)
• Mobile Application (ridewithme_mobile)
• Backend Services
• Main API (ridewithme.API)
• RabbitMQ Service (ridewithme.RabbitMQ)
• Database Layer (evident from the RidewithmeContext)
• Message Queue System (RabbitMQ)
┌─────────────────────┐ ┌─────────────────────┐
• Mobile App │ │ Admin Panel │
• (Flutter) │ │ (Flutter) │
• ┘ └─────────────────────┘
┌─────────────────────────────────────────────┐
• ridewithme.API │
• (Controllers, Authentication, Services) │
• ┘
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
• Voznje │ │ Korisnici │ │ Zalbe │
• Service │ │ Service │ │ Service │
• ┘ └─────────────┘ └─────────────┘
┌─────────────────────────────────────────────┐
• RabbitMQ Service │
• (Email Notifications, State Changes) │
• ┘
┌─────────────────────────────────────────────┐
• RidewithmeContext (DB) │
• ┘
Key Relationships to Highlight
• State machine flows for:
• Kuponi (Draft → Active → Hidden)
• Voznje (Draft → Active → Booked → Hidden)
• Zalbe (Initial → Active → Processing → Completed)
• Database relationships between key entities
Additional Elements
• Authentication flow indicators
• External service integrations
• Error handling paths
Technical Details
• Docker container boundaries
• API endpoints grouping
• Database entity relationships
• State machine transitions
• Message queue topics/channels