How fercaires/liveloscrapper works
LiveloScrapper fetches Livelo partner data, extracts partner and parity details, then filters results for console ranking and optional Telegram notification while saving complete JSON and CSV snapshots. The entry point runs once or starts the daily scheduler. The README documents Docker and GitHub Actions execution, but these are deployment mechanisms rather than runtime product components; source confirms the workflow and storage behavior shown here.
Main entry points: scheduler.py Job scheduler · scraper.py Partner scraper · main.py CLI entry · storage.py File storage
Components 13
Execution
- CLI entry
main.py - Job scheduler
src/scheduler.py
Partner collection
- Partner scraper
src/scraper.py - Partner model
src/models/partner.py - Parity model
src/models/parity.py
Processing
- Category filter
src/filters.py
Results and notifications
- File storage
src/storage.py - JSON and CSV
data - Telegram notifier
src/notifier.py
Other components
- Operator
- Schedule library
- Livelo site
- Telegram API
Connections 14
- Operator → CLI entry: runs
- CLI entry → Job scheduler: runs job
- CLI entry → Job scheduler: starts schedule
- Schedule library → Job scheduler: dispatches job
- Job scheduler → Partner scraper: scrapes partners
- Partner scraper → Livelo site: fetches page
- Partner scraper → Partner model: constructs
- Partner scraper → Parity model: constructs
- Job scheduler → File storage: saves results
- File storage → Partner scraper: serializes data
- File storage → JSON and CSV: writes JSON and CSV
- Job scheduler → Category filter: filters partners
- Job scheduler → Telegram notifier: notifies
- Telegram notifier → Telegram API: sends message