How rfned/astralteam works
Astral Team is a game-store and gaming-platform web application. Its visible workflow runs from account registration or login through HTTP requests, backend user services, and session/profile state; registration also includes email verification. The backend exposes a separate balance/payment capability, while the frontend includes game, community, news, profile, and launcher pages. The graph follows documented and indexed imports; game-catalog, library, ratings, and statistics behavior is described in the README but is not established by the sampled implementation. Backend wiring beyond indexed references is not assumed.
Main entry points: dependencies.py Dependency wiring · core.tsx Page routing · client.ts HTTP client · user.py User workflows
Components 22
Web client
- Page routing
frontend/src/core.tsx - Launcher home
frontend/src/Pages/Main/main.tsx - Games & community
frontend/src/Pages/Games/games.tsx - News
frontend/src/Pages/News/news.tsx - Profile
frontend/src/Pages/Profile/profile.tsx - Login
frontend/src/Pages/Auth/auth.tsx - Registration
frontend/src/Pages/Auth/Reg/reg.tsx - Email verification
frontend/src/Pages/Special/VerifyEmail/verifyemail.tsx - Session state
frontend/src/Contexts/authContext.tsx - HTTP client
frontend/src/Api/client.ts
Backend API
- User endpoints
backend/api/user.py - Balance endpoints
backend/api/balance.py - Dependency wiring
backend/api/dependencies.py
Domain services
- User workflows
backend/services/user.py - Payment workflow
backend/services/balance.py - User records
backend/repositories/user.py - Balance records
backend/repositories/balance.py
Infrastructure
- Verification email
backend/core/email.py - MySQL
backend/core/database.py - Redis
backend/core/redis.py - YooKassa
backend/core/yookassa.py
Other components
- Visitor
Connections 31
- Visitor → Page routing: uses
README.md - Page routing → Launcher home: routes to
frontend/src/core.tsx - Page routing → Games & community: routes to
frontend/src/core.tsx - Page routing → News: routes to
frontend/src/core.tsx - Page routing → Profile: routes to
frontend/src/core.tsx - Page routing → Login: routes to
frontend/src/core.tsx - Page routing → Registration: routes to
frontend/src/core.tsx - Page routing → Email verification: routes to
frontend/src/core.tsx - Login → HTTP client: calls
frontend/src/Pages/Auth/auth.tsx - Registration → HTTP client: calls
frontend/src/Pages/Auth/Reg/reg.tsx - Email verification → HTTP client: calls
frontend/src/Pages/Special/VerifyEmail/verifyemail.tsx - Session state → HTTP client: loads session
frontend/src/Contexts/authContext.tsx - HTTP client → User endpoints: HTTP requests
README.md - User endpoints → Dependency wiring: resolves services
backend/api/user.py - Balance endpoints → Dependency wiring: resolves services
backend/api/balance.py - Dependency wiring → User workflows: constructs
backend/api/dependencies.py - Dependency wiring → Payment workflow: constructs
backend/api/dependencies.py - Dependency wiring → User records: constructs
backend/api/dependencies.py - Dependency wiring → Balance records: constructs
backend/api/dependencies.py - Dependency wiring → MySQL: gets connection
backend/api/dependencies.py - Dependency wiring → Redis: gets client
backend/api/dependencies.py - Dependency wiring → Verification email: constructs
backend/api/dependencies.py - Dependency wiring → YooKassa: gets client
backend/api/dependencies.py - User workflows → User records: reads and writes
backend/services/user.py - User workflows → Verification email: sends verification
backend/services/user.py - User workflows → Redis: stores sessions
backend/services/user.py - Payment workflow → Balance records: reads and writes
backend/services/balance.py - Payment workflow → Redis: checks session
backend/services/balance.py - Payment workflow → YooKassa: creates payment
backend/services/balance.py - User records → MySQL: executes SQL
- Balance records → MySQL: executes SQL