KiteAgent documentation

Features

• PWA subscription page, Web Push subscribe and unsubscribe, VAPID keys, welcome push on subscribe and /test-push for diagnostics.
• JSON /forecast (latest stored forecast plus rideable windows from the last analysis) and /status (health-style snapshot from SQLite).
• Authenticated POST /push (Bearer secret) to fan out notifications to all stored subscriptions.
• Admin-only POST /pull (matching configured user) to fetch forecast from a configurable HRRR base URL and insert it into the shared database.
• Optional GET /live proxy to live-server when [live] HTTP URL is set in config.
• Agent (separate process): scheduled fetch of HRRR-shaped forecast (local hrrr-server in debug builds, remote in release), rideable-window evaluation against gear, opportunity alerts and morning digest via POST /push, optional live-wind checks over gRPC to live-server.

Architecture

Typical deployment: agent and server share one SQLite file (storage.db_path in config.toml). Optional services are wired when you run hrrr-server, live-server, and config blocks.

flowchart LR
  subgraph forecastData [Forecast_data]
    NOMADS[NOMADS_HRRR]
  end
  NOMADS --> hrrr[hrrr_server]
  hrrr -->|"HTTP /forecast"| agent[kiteagent_agent]
  arl[ARL_UT_Lake_Travis] --> live[live_server]
  live -->|gRPC_GetLatest| agent
  agent -->|POST_push| ks[kiteagent_server]
  agent --> db[(SQLite)]
  ks --> db
  browser[Browser_PWA] -->|subscribe_static| ks
  ks -->|Web_Push| push[Push_gateways]