How david-lor/vigobus-telegrambot works
VigoBus-TelegramBot is an async Telegram backend for searching Vigo bus stops, showing real-time arrivals, and managing saved stops. Users enter through Telegram messages, inline queries, or callback buttons; handlers invoke stop lookup or saved-stop operations and generate replies. Separate features support stop renaming, feedback, and user-data export/deletion. The README documents the external VigoBus and Persistence APIs and MongoDB-backed request logs. Some runtime wiring is unsampled, so edges not supported by excerpts or README are omitted.
Main entry points: message_handlers.py Message handlers · saved_stops_manager.py Saved stops · message_generators Reply generation · callback_handlers.py Button handlers
Components 22
Bot runtime
- Application startup
vigobusbot/entrypoint.py - Bot runtime
vigobusbot/telegram_bot/bot.py - Update delivery
vigobusbot/telegram_bot/polling.py
User interactions
- Message handlers
vigobusbot/telegram_bot/handlers/message_handlers.py - Inline handlers
vigobusbot/telegram_bot/handlers/inline_handlers.py - Button handlers
vigobusbot/telegram_bot/handlers/callback_handlers.py - Request controls
vigobusbot/telegram_bot/services/generic_request_handler/request_handler.py - Reply generation
vigobusbot/telegram_bot/services/message_generators - Rename and feedback
vigobusbot/telegram_bot/services
Transit data
- Stop lookup
vigobusbot/vigobus_api/stop_getter.py - Bus arrivals
vigobusbot/vigobus_api/bus_getter.py
Persistence
- Saved stops
vigobusbot/persistence_api/saved_stops/saved_stops_manager.py - Saved-stop encoding
vigobusbot/persistence_api/saved_stops/services/encoder.py - Sent-message state
vigobusbot/telegram_bot/services/sent_messages_persistence.py
Bot operations
- Static content
vigobusbot/static_handler - Configuration
vigobusbot/settings_handler/__init__.py - Request logging
vigobusbot/logger.py
Other components
- Telegram user
- Telegram platform
- VigoBus API
- Persistence API
- MongoDB logs
Connections 26
- Telegram user → Telegram platform: sends updates
- Telegram platform → Bot runtime: delivers updates
- Application startup → Bot runtime: starts
- Application startup → Static content: loads
vigobusbot/entrypoint.py - Bot runtime → Update delivery: runs
- Update delivery → Telegram platform: receives updates
- Message handlers → Request controls: wraps requests
vigobusbot/telegram_bot/handlers/message_handlers.py - Button handlers → Request controls: wraps requests
vigobusbot/telegram_bot/handlers/callback_handlers.py - Message handlers → Reply generation: generates replies
vigobusbot/telegram_bot/handlers/message_handlers.py - Button handlers → Reply generation: generates replies
vigobusbot/telegram_bot/handlers/callback_handlers.py - Inline handlers → Reply generation: generates results
vigobusbot/telegram_bot/handlers/inline_handlers.py - Message handlers → Rename and feedback: handles replies
vigobusbot/telegram_bot/handlers/message_handlers.py - Button handlers → Saved stops: updates saved stops
vigobusbot/telegram_bot/handlers/callback_handlers.py - Rename and feedback → Saved stops: renames stops
vigobusbot/telegram_bot/services/stop_rename_request_handler.py - Rename and feedback → Reply generation: refreshes message
vigobusbot/telegram_bot/services/stop_rename_request_handler.py - Reply generation → Stop lookup: formats stop replies
- Message handlers → Stop lookup: searches stops
- Stop lookup → VigoBus API: requests stop data
vigobusbot/vigobus_api/stop_getter.py - Bus arrivals → VigoBus API: requests arrival data
- Message handlers → Saved stops: manages saved stops
vigobusbot/telegram_bot/handlers/message_handlers.py - Saved stops → Saved-stop encoding: encodes records
vigobusbot/persistence_api/saved_stops/saved_stops_manager.py - Saved stops → Persistence API: persists stops
- Sent-message state → Saved-stop encoding: uses encoding
vigobusbot/telegram_bot/services/sent_messages_persistence.py - Message handlers → Sent-message state: tracks messages
vigobusbot/telegram_bot/handlers/message_handlers.py - Request logging → MongoDB logs: persists request logs
vigobusbot/logger.py - Request logging → Configuration: reads settings
vigobusbot/logger.py