How romka14/gym_bot works
Gym Tracker Bot is a Telegram workout tracker. The main workflow starts with a user creating a workout, selecting exercises, and logging sets; the bot can then finish the workout and provide history, statistics, and personal records. The graph separates Telegram interaction, domain services, persistence, and relational models. The README documents history and statistics capabilities, while excerpts show selected workout, reference-data, and persistence calls; unsampled details are represented only where documented, without inferred call edges.
Main entry points: connection.py Async database session · main.py Command handlers · workout_service.py Workout lifecycle · base.py CRUD repository
Components 18
Telegram interface
- Command handlers
app/main.py - Conversation state
app/states.py
Workout services
- User service
app/services/user_service.py - Exercise catalog
app/services/reference_service.py - Workout lifecycle
app/services/workout_service.py
Persistence
- User repository
app/repositories/user_repository.py - Muscle group repository
app/repositories/muscle_group_repository.py - Exercise repository
app/repositories/exercise_repository.py - CRUD repository
app/repositories/base.py - Async database session
app/database/connection.py
Workout data
- User records
app/models/user.py - Muscle groups
app/models/muscle_group.py - Exercise catalog
app/models/exercise.py - Workouts
app/models/workout.py - Workout exercises
app/models/workout_exercise.py - Workout sets
app/models/workout_set.py
Other components
- Telegram user
- Telegram Bot API
Connections 30
- Telegram user → Telegram Bot API: sends commands
README.md - Telegram Bot API → Command handlers: delivers updates
app/main.py - Command handlers → Telegram Bot API: sends replies
app/main.py - Command handlers → Conversation state: tracks conversation
app/main.py - Command handlers → User service: gets or creates
app/main.py - Command handlers → Exercise catalog: loads catalog
app/main.py - Command handlers → Workout lifecycle: manages workout
app/main.py - Exercise catalog → Muscle group repository: queries groups
app/services/reference_service.py - Exercise catalog → Exercise repository: queries exercises
app/services/reference_service.py - User service → User repository: uses repository
- Workout lifecycle → Async database session: queries and writes
app/services/workout_service.py - User repository → CRUD repository: inherits CRUD
app/repositories/user_repository.py - Muscle group repository → CRUD repository: inherits CRUD
app/repositories/muscle_group_repository.py - Exercise repository → CRUD repository: inherits CRUD
app/repositories/exercise_repository.py - CRUD repository → Async database session: executes queries
app/repositories/base.py - User repository → User records: operates on
app/repositories/user_repository.py - Muscle group repository → Muscle groups: operates on
app/repositories/muscle_group_repository.py - Exercise repository → Exercise catalog: operates on
app/repositories/exercise_repository.py - Async database session → User records: maps records
app/models/user.py - Async database session → Muscle groups: maps records
app/models/muscle_group.py - Async database session → Exercise catalog: maps records
app/models/exercise.py - Async database session → Workouts: maps records
app/models/workout.py - Async database session → Workout exercises: maps records
app/models/workout_exercise.py - Async database session → Workout sets: maps records
app/models/workout_set.py - Workout lifecycle → Workouts: creates and queries
app/services/workout_service.py - Workout lifecycle → Workout exercises: adds exercises
app/services/workout_service.py - Workout lifecycle → Workout sets: adds sets
app/services/workout_service.py - Workouts → Workout exercises: relates exercises
app/models/workout.py - Workout exercises → Workout sets: contains sets
app/models/workout_exercise.py - Muscle groups → Exercise catalog: groups exercises
app/models/muscle_group.py