How jc0510004/free_ricky works
FREE_RICKY is a game-community web application with a React client and Django API. Visitors browse the public landing page; account registration, login, and session restoration support access to protected game, settings, and administration areas. The backend also has distinct user, game, email, and admin capabilities. The excerpts show client authentication and API mechanics plus backend authentication and security behavior; several domain endpoints are represented from the file tree and source index, so their internal call paths are not asserted.
Main entry points: main.jsx Router and entry · authService.js Auth API service · pages Account and game pages · AuthContext.jsx Session provider
Components 20
Web client
- Router and entry
frontend/src/main.jsx - Public landing
frontend/src/App.jsx - Account and game pages
frontend/src/pages - Admin dashboard
frontend/src/pages/Admin.jsx
Identity and access
- Session provider
frontend/src/contexts/AuthContext.jsx - Auth consumer hook
frontend/src/contexts/useAuth.js - Auth API service
frontend/src/services/authService.js - Access token state
frontend/src/api/tokenStore.js - HTTP client
frontend/src/api/axios.js
Backend API
- Authentication endpoints
backend/api/views_auth.py - Request serializers
backend/api/serializers.py - User and game data
backend/api/models.py - Game and user APIs
backend/api - Email workflows
backend/api/views_email.py - Admin API
backend/api/views_admin.py
Security and operations
- Request security
backend/api/middleware.py - Hardened admin login
backend/config/admin_site.py - Django cache
Other components
- Visitor
- Browser user
Connections 21
- Visitor → Router and entry: opens
frontend/src/main.jsx - Browser user → Router and entry: uses
- Router and entry → Public landing: routes to
frontend/src/main.jsx - Router and entry → Account and game pages: routes to
frontend/src/main.jsx - Router and entry → Session provider: wraps routes
frontend/src/main.jsx - Router and entry → Admin dashboard: lazy-loads
- Public landing → Auth consumer hook: reads session
frontend/src/App.jsx - Session provider → Auth API service: calls
frontend/src/contexts/AuthContext.jsx - Auth consumer hook → Session provider: reads context
frontend/src/contexts/useAuth.js - Auth API service → HTTP client: sends requests
frontend/src/services/authService.js - Auth API service → Access token state: updates token
frontend/src/services/authService.js - HTTP client → Access token state: reads and updates
frontend/src/api/axios.js - Auth API service → Authentication endpoints: calls auth routes
- Authentication endpoints → Request serializers: validates input
backend/api/views_auth.py - Request serializers → User and game data: uses models
backend/api/serializers.py - Account and game pages → Game and user APIs: requests domain APIs
- Account and game pages → Email workflows: requests email APIs
- Admin dashboard → Admin API: requests admin APIs
- Hardened admin login → Request security: checks IP
backend/config/admin_site.py - Hardened admin login → Django cache: throttles via
- Request security → Django cache: tracks attempts
backend/api/middleware.py