apt/fuelboard
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Backlog: P0 GitHub mirror — capture telemetry implications (widget beacon survives, opportunistic app beacon, /stats canary + fallback-outage signal)

Browse Source
This commit is contained in:
FuelBoard Contributor
2026-08-15 08:43:59 +01:00
parent 817a829107
commit 0545659c1b
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
BACKLOG.md
+7 -1
View File
@@ -21,7 +21,13 @@ Status: TODO / IN PROGRESS / DONE / BLOCKED.
fetches `raw.githubusercontent.com/aptonline/fuelboard-data/main/latest.json`, fetches `raw.githubusercontent.com/aptonline/fuelboard-data/main/latest.json`,
then only the missing day files for starred (station, fuel) pairs (deterministic then only the missing day files for starred (station, fuel) pairs (deterministic
URLs — 404 = no data that day, leave a graph gap, never error). LAN relay stays URLs — 404 = no data that day, leave a graph gap, never error). LAN relay stays
the fallback source. Setup: create the PUBLIC repo `aptonline/fuelboard-data` the fallback source. Telemetry implication: raw GitHub fetches are invisible to
repo analytics (page views/clones only) — keep the widget-diag beacon firing
regardless of data source (build/stale-build checks survive) and add an
opportunistic fire-and-forget X-Client app beacon on fetch (LAN = attribution +
cadence; off-LAN skip is itself a reachability datum). `/stats` keeps the
intrusion canary and gains a new signal: app-hit spikes = GitHub path failing →
fallback active. Setup: create the PUBLIC repo `aptonline/fuelboard-data`
(gh installed); GitHub PAT (aptonline) lives in relay `.env` only — never in the (gh installed); GitHub PAT (aptonline) lives in relay `.env` only — never in the
repo or IPA. App Review: public repo required (reviewer fetches the data repo or IPA. App Review: public repo required (reviewer fetches the data
themselves); HTTPS/ATS fine; plain JSON is not "remote code" (2.5.2-safe); bundle themselves); HTTPS/ATS fine; plain JSON is not "remote code" (2.5.2-safe); bundle