How ngamaniprasad/django_react_ipl works
CricketHub is a React/Django IPL management and information application. Users register or sign in, then browse teams and their players, fixtures, statistics, standings, and available downloads; administrators have separate routes for managing cricket records and accounts. The graph preserves those product branches and the backend model, serialization, and statistics layers. Edges are limited to relationships shown in excerpts, the source index, or README; unsampled service-to-API wiring is not asserted.
Main entry points: settings.py Django configuration · AppRoutes.jsx Page routes · matches/models.py Match endpoints and records · players/models.py Player records
Components 24
React application
- React app
frontend/src/App.jsx - Page routes
frontend/src/routes/AppRoutes.jsx - Public pages
frontend/src/pages/public - Login and register
frontend/src/pages/auth - User views
frontend/src/pages/user - Admin management
frontend/src/pages/admin - API client
frontend/src/services/api.jsx
Accounts
- Account endpoints
backend/accounts/views.py - Account serializers
backend/accounts/serializers.py - User records
backend/accounts/models.py
Cricket records
- Team records
backend/teams/models.py - Player records
backend/players/models.py - Tournament records
backend/tournaments/models.py - Match endpoints and records
backend/matches/models.py - Match serialization
backend/matches/serializers.py - Points table
backend/points_table/models.py - Points serialization
backend/points_table/serializers.py
Insights and exports
- Player statistics
backend/stats/views.py - Statistics serialization
backend/stats/serializers.py - CSV downloads
backend/downloads/views.py - Media management
backend/media_manager/views.py
Django platform
- Django configuration
backend/config/settings.py - MySQL database
Other components
- Visitor
Connections 30
- Visitor → Page routes: opens pages
frontend/src/routes/AppRoutes.jsx - React app → Page routes: renders
frontend/src/App.jsx - Page routes → Public pages: routes to
frontend/src/routes/AppRoutes.jsx - Page routes → Login and register: routes to
frontend/src/routes/AppRoutes.jsx - Page routes → User views: routes to
frontend/src/routes/AppRoutes.jsx - Page routes → Admin management: routes to
frontend/src/routes/AppRoutes.jsx - Login and register → Account endpoints: uses API
- User views → API client: uses client
- Admin management → API client: uses client
- Account endpoints → Account serializers: serializes
- Account serializers → User records: models
backend/accounts/serializers.py - Django configuration → Account endpoints: configures
- Django configuration → Match endpoints and records: configures
- Django configuration → Player statistics: configures
- Django configuration → CSV downloads: configures
- Django configuration → Media management: configures
- Match endpoints and records → Match serialization: serializes
backend/matches/serializers.py - Match serialization → Match endpoints and records: models
backend/matches/serializers.py - Points serialization → Points table: models
backend/points_table/serializers.py - Player records → Team records: references team
backend/players/models.py - Match endpoints and records → Team records: references teams
backend/matches/models.py - Match endpoints and records → Tournament records: references tournament
backend/matches/models.py - Points table → Team records: references team
backend/points_table/models.py - Points table → Tournament records: references tournament
backend/points_table/models.py - Player statistics → Player records: queries players
backend/stats/views.py - Player statistics → Statistics serialization: serializes results
backend/stats/views.py - Statistics serialization → Player records: models
backend/stats/serializers.py - CSV downloads → Player records: exports players
backend/downloads/views.py - CSV downloads → Team records: exports teams
backend/downloads/views.py - Django configuration → MySQL database: configures store