How soloofboom/rifterm works
rifterm is a terminal client for RIF market data. Users save an API key, then check its validity and quota or request Heat Index and pépites data over a chosen day window. Those data commands use a five-minute local cache unless disabled, then render either rich terminal tables or raw JSON. The README also documents cache controls and quota behavior. The tree and sampled source support no separate report workflow; report is only a roadmap item.
Main entry points: cli.py CLI commands · client.py HTTP client · cache.py TTL cache · config.py API key config
Components 10
CLI commands
- CLI commands
src/rifterm/cli.py
Market data
- HTTP client
src/rifterm/client.py - RIF API
Local state
- API key config
src/rifterm/config.py - Config file
src/rifterm/config.py - TTL cache
src/rifterm/cache.py - Cached payloads
src/rifterm/cache.py
Output
- Heat and pépites rendering
src/rifterm/render.py
Other components
- User
- Terminal output
Connections 13
- User → CLI commands: runs commands
- CLI commands → API key config: saves or loads key
- API key config → Config file: reads and writes
- CLI commands → TTL cache: fetches market data
- TTL cache → Cached payloads: reads and writes
- TTL cache → HTTP client: miss calls
- CLI commands → HTTP client: checks status
- HTTP client → RIF API: sends GET
- RIF API → HTTP client: returns response
- TTL cache → CLI commands: returns payload
- HTTP client → CLI commands: returns status response
- CLI commands → Heat and pépites rendering: renders payload
- Heat and pépites rendering → Terminal output: prints tables or JSON