How interact-club-of-bishkek/interact-backend works
Interact Club Backend supports volunteer applications, club administration, teams and projects, with a Telegram bot offering application flows and group games. The main web flow is an applicant or administrator using Django/DRF endpoints to submit or manage volunteer records; teams and projects are separate domain capabilities, and Finik handles project-payment operations. The bot runner registers application, volunteer, project-creation, and game routers. Relationships are limited to README statements and indexed or excerpted references; unsampled web routes and model persistence details are not inferred.
Main entry points: views.py Volunteer API · bot_runner.py Bot runner · urls.py API routing · models.py Project records
Components 25
Web API
- API routing
interact/urls.py - Volunteer API
users/views.py - Volunteer serialization
users/serializers.py
Club management
- Volunteer records
users/models.py - Command management
commands/views.py - Command records
commands/models.py - Project management
projects/views.py - Project records
projects/models.py
Payments
- Finik payment API
finik/views.py - Payment records
finik/models.py - Finik service
Telegram bot
- Application flow
telegram_bot/volunteers/telegram_handlers.py - Bot runner
telegram_bot/bot_runner.py - General handlers
telegram_bot/general/handlers.py - Volunteer auth check
telegram_bot/volunteers/auth_check.py - Project creation flow
telegram_bot/volunteers/project_creation.py
Bot games
- Crocodile handlers
telegram_bot/crocodile/crocodile_runner.py - Crocodile game logic
telegram_bot/crocodile/crocodile_game.py - Mafia handlers
telegram_bot/mafia/handlers.py - Mafia game logic
telegram_bot/mafia/game.py - Mafia game storage
telegram_bot/mafia/storage.py
Other components
- Applicant
- Club administrator
- Telegram users
- PostgreSQL
Connections 31
- Applicant → API routing: uses API
- Club administrator → API routing: uses API
- API routing → Volunteer API: routes to
interact/urls.py - Volunteer API → Volunteer records: reads and writes
users/views.py - Volunteer API → Volunteer serialization: serializes
users/views.py - Volunteer API → Command records: uses command
users/views.py - Volunteer API → Project records: uses project
users/views.py - Club administrator → Command management: manages teams
- Command management → Command records: reads and writes
commands/views.py - Club administrator → Project management: manages projects
- Project management → Project records: reads and writes
projects/views.py - API routing → Project management: routes to
- Finik payment API → Payment records: reads and writes
finik/views.py - Finik payment API → Project records: reads project
finik/views.py - Finik payment API → Finik service: sends requests
finik/views.py - Telegram users → Bot runner: interacts with
- Bot runner → Application flow: registers router
telegram_bot/bot_runner.py - Bot runner → Project creation flow: registers router
telegram_bot/bot_runner.py - Bot runner → General handlers: registers router
telegram_bot/bot_runner.py - Bot runner → Crocodile handlers: registers router
telegram_bot/bot_runner.py - Bot runner → Mafia handlers: registers router
telegram_bot/bot_runner.py - Application flow → Volunteer API: submits application
telegram_bot/volunteers/telegram_handlers.py - General handlers → Volunteer auth check: checks password
telegram_bot/general/handlers.py - Volunteer auth check → Volunteer API: posts credentials
telegram_bot/volunteers/auth_check.py - Crocodile handlers → Crocodile game logic: starts rounds
telegram_bot/crocodile/crocodile_runner.py - Mafia handlers → Mafia game logic: runs game logic
telegram_bot/mafia/handlers.py - Mafia handlers → Mafia game storage: loads and saves
telegram_bot/mafia/handlers.py - Mafia game storage → Mafia game logic: recreates game
telegram_bot/mafia/storage.py - Volunteer records → PostgreSQL: persists in
- Command records → PostgreSQL: persists in
- Project records → PostgreSQL: persists in