How sirfilips/centmeta-backend works
CentMeta is a backend for Centurion Commander metagame analysis. The primary workflow is decklist acquisition from Moxfield, storage in SQLite, statistical aggregation, and REST API responses to the frontend, enriched with Scryfall card metadata. The README also documents caching, automated database refresh and cache warming, and an optional community-voting feature. The implementation is concentrated in two large Python files; unsampled capabilities are represented at the documented subsystem level, without assuming their internal call structure.
Main entry points: main.py REST API · master_scraper.py Deck scraper
Components 12
Deck ingestion
- Deck scraper
master_scraper.py
API and analytics
- REST API
main.py - Metagame statistics
main.py - Response caches
main.py - SQLite database
main.py - Refresh and prewarm
main.py - Deck administration
main.py
Metadata and community
- Card metadata resolution
main.py - Community Observatory
main.py
Other components
- Frontend
- Moxfield
- Scryfall API
Connections 14
- Frontend → REST API: requests
README.md - REST API → Metagame statistics: dispatches
main.py - Metagame statistics → SQLite database: queries
README.md - Metagame statistics → Card metadata resolution: resolves cards
main.py - REST API → Response caches: uses
README.md - Refresh and prewarm → SQLite database: refreshes
README.md - Refresh and prewarm → Response caches: warms
README.md - Deck scraper → Moxfield: fetches decks
master_scraper.py - Deck scraper → SQLite database: writes decks
README.md - REST API → Deck scraper: pings via limiter
main.py - Card metadata resolution → Scryfall API: fetches metadata
README.md - REST API → Community Observatory: serves voting
README.md - REST API → Deck administration: routes admin actions
main.py - Deck administration → SQLite database: removes decks
README.md