How illiagerega/concert.in.ua works
concert.in.ua is a Telegram ticket-sales bot. Users start the bot, provide contact details for their profile, browse events by city and event, choose ticket type and quantity, and proceed through payment; successful-payment handling creates tickets. Users can also view their profile and existing tickets, and contact support. The graph separates bot workflows, ticket and profile data, and shared utilities. The excerpts show SQLite access and several calls, but omit parts of the purchase handlers, so unshown relationships are not inferred.
Main entry points: main.py Bot handlers · logs.py Activity logging · profile.py Profile operations · db.py Ticket operations
Components 15
Bot workflows
- Bot handlers
main.py - Profile and contact
main.py - City and event browse
main.py - Ticket selection
main.py - Payment handling
main.py - View tickets
main.py - Support menu
main.py
Ticket and profile data
- Profile operations
profile.py - Ticket operations
db.py - SQLite database
db.db
Shared utilities
- Activity logging
logs.py - Ticket ID and time
ticket.py - Bot and DB config
config.py
Other components
- Telegram user
- Telegram platform
Connections 23
- Telegram user → Bot handlers: sends commands
main.py - Bot handlers → Telegram platform: sends messages
main.py - Bot handlers → Profile and contact: routes profile actions
main.py - Bot handlers → City and event browse: routes buy flow
main.py - Bot handlers → Ticket selection: routes selections
main.py - Bot handlers → Payment handling: handles payment
main.py - Bot handlers → View tickets: loads tickets
main.py - Bot handlers → Support menu: shows help
main.py - Bot handlers → Profile operations: calls profile operations
main.py - Bot handlers → Ticket operations: calls ticket operations
main.py - Bot handlers → Activity logging: records user actions
main.py - Profile operations → SQLite database: reads and writes
profile.py - Profile operations → Ticket ID and time: gets current time
profile.py - Profile operations → Activity logging: logs operations
profile.py - Ticket operations → SQLite database: reads and writes
db.py - Ticket operations → Ticket ID and time: generates ID and time
db.py - Ticket operations → Activity logging: logs operations
db.py - Activity logging → SQLite database: writes log records
logs.py - Activity logging → Ticket ID and time: gets current time
logs.py - Profile operations → Bot and DB config: uses DB config
profile.py - Ticket operations → Bot and DB config: uses DB config
db.py - Activity logging → Bot and DB config: uses DB config
logs.py - Bot handlers → Bot and DB config: uses bot config
main.py