How kasemsak66/eventflow works
Eventflow is a Django venue-booking and community-activity application. Users discover venues, book them and submit payment slips; owners manage venues and bookings, then completed bookings can support reviews and activities. The app also provides account/profile features, favorites, analytics, staff administration, and WebSocket chat. The graph follows the documented URL and WebSocket routing and the sampled view/model relationships; some detailed subsystems are represented by their source modules because their implementations were not fully sampled.
Main entry points: models.py Domain records · urls.py HTTP routes · forms.py Domain forms · auth_views.py Accounts and profile
Components 18
Accounts
- Accounts and profile
mylogin/views/auth_views.py - Account forms
mylogin/forms.py
Venue discovery
- Venue management
mylogin/views/venue_views.py - Venue discovery
mylogin/views/landing_views.py - Venue map
mylogin/views/venue_views.py - Domain forms
mylogin/forms.py
Bookings and payments
- Booking and payment
mylogin/views/booking_views.py - Domain records
mylogin/models.py - Application database
Activities and community
- Activities and signup
mylogin/views/activity_views.py - Venue reviews
mylogin/views/review_views.py
Administration and chat
- WebSocket routes
mylogin/routing.py - Chat history
mylogin/views/chat_views.py - Live chat
mylogin/consumers.py - Staff administration
mylogin/views/admin_views.py
Other components
- User
- HTTP routes
mylogin/urls.py - Chat client
Connections 28
- User → HTTP routes: sends requests
mylogin/urls.py - HTTP routes → Accounts and profile: routes to
mylogin/urls.py - HTTP routes → Venue management: routes to
mylogin/urls.py - HTTP routes → Venue discovery: routes to
mylogin/urls.py - HTTP routes → Booking and payment: routes to
mylogin/urls.py - HTTP routes → Activities and signup: routes to
mylogin/urls.py - HTTP routes → Venue reviews: routes to
mylogin/urls.py - HTTP routes → Staff administration: routes to
mylogin/urls.py - HTTP routes → Chat history: routes to
- Accounts and profile → Account forms: uses
mylogin/views/auth_views.py - Accounts and profile → Domain records: reads and updates
mylogin/views/auth_views.py - Venue management → Domain forms: uses
mylogin/views/venue_views.py - Venue management → Domain records: reads and updates
mylogin/views/venue_views.py - Venue discovery → Domain records: searches
mylogin/views/landing_views.py - Venue map → Domain records: reads
mylogin/views/venue_views.py - Booking and payment → Domain forms: uses
mylogin/views/booking_views.py - Booking and payment → Domain records: reads and updates
mylogin/views/booking_views.py - Activities and signup → Domain forms: uses
mylogin/views/activity_views.py - Activities and signup → Domain records: reads and updates
mylogin/views/activity_views.py - Venue reviews → Domain forms: uses
mylogin/views/review_views.py - Venue reviews → Domain records: checks and updates
mylogin/views/review_views.py - Staff administration → Domain records: manages
mylogin/views/admin_views.py - Chat history → Domain records: reads
mylogin/views/chat_views.py - Domain forms → Domain records: validates
mylogin/forms.py - Domain records → Application database: persists records
mylogin/models.py - Chat client → WebSocket routes: opens socket
mylogin/routing.py - WebSocket routes → Live chat: dispatches to
mylogin/routing.py - Live chat → Domain records: uses
mylogin/consumers.py