How hackerheroop/msg-scheduler works
This is a Telegram channel-post scheduler with administrative controls for channels and scheduled posts, plus HTTP health checks. The visible main workflow is bot startup and command handling; scheduling and delivery are also represented in main.py and in a separate scheduler.py implementation. The excerpts do not establish that the standalone scheduler is wired into bot startup, or show all command registrations and persistence calls, so those relationships are omitted.
Main entry points: scheduler.py Scheduler Loop · main.py Bot Admin · database.py Post Storage · start.py HTTP Health Server
Components 11
Bot Runtime
- Bot Admin
main.py - Channel Controls
main.py - Bot Startup
main.py
Post Scheduling
- Post Scheduling
main.py - Scheduled Delivery
main.py - Scheduler Loop
scheduler.py
Persistence
- Post Storage
database.py - MongoDB
Health Checks
- HTTP Health Server
start.py
Other components
- Health Probe
- Telegram
Connections 8
- Bot Startup → Bot Admin: runs bot
main.py - Health Probe → HTTP Health Server: requests health
- HTTP Health Server → Bot Startup: starts bot
start.py - Scheduler Loop → Post Storage: fetches and updates
scheduler.py - Post Storage → MongoDB: persists posts
database.py - Scheduler Loop → Telegram: sends posts
scheduler.py - Post Scheduling → Scheduled Delivery: dispatches due posts
main.py - Bot Admin → Channel Controls: offers controls
main.py