How drehelis/sammy_ofer works
Main Components
a) Web Scraping Layer
• Web scraper component (web_scrape.py)
• Connection to the external Sammy Ofer Stadium website
b) Scheduling System
• Cron scheduler (cron.py)
• How it triggers the web scraping process
c) Data Storage
• Currently using dictionary storage (as mentioned in TODO about future SQLite implementation)
• As a temporary data store
d) Notification System
• Telegram Bot integration
• Connection to Telegram API
e) Web Interface
• Flask web server (web.py)
• Static page generator (static_html_page.py)
• Template rendering system (using Jinja2)
[External Sources]
• ↓
[Web Scraper]
• ↓
[Scheduler] ←→ [Data Store]
• ↓
[Core Logic]
• ↓
[Output Layer]
• ↙ ↘
[Telegram] [Web UI]
Important Relationships
• Scheduler triggering the web scraper
• Web scraper updating the data store
• Core logic reading from data store
• Template system feeding into both web UI and static page generation
• Notification system pushing to Telegram
Technical Details
• Flask web server on port 5000
• Jinja2 templating system
• Cron-based scheduling
• Docker containerization
• GitHub Actions CI/CD pipeline
[Configuration]
• Environment Variables
• Docker Settings
• Development Container
[Core Application]
• Web Scraper
• Scheduler
• Data Management
[Output Interfaces]
• Web UI (Flask)
• Static Page
• Telegram Bot
[Infrastructure]
• Docker Container
• GitHub Actions
• GitHub Pages
This architecture should be represented in a way that highlights both the simplicity of the core functionality (web scraping and notifications) and the professional implementation details (containerization, CI/CD, multiple output formats).