Skip to content

20260926 - Point the tar1090 ADS-B fallback at adsb.retina.fm first - #44

Merged
Purple10101 merged 1 commit into
mainfrom
feat/adsb-upstream-chain
Sep 27, 2026
Merged

Purple10101 merged 1 commit into
mainfrom
feat/adsb-upstream-chain

Conversation

@Purple10101

@Purple10101 Purple10101 commented Sep 25, 2026 •

Copy link
Copy Markdown
Collaborator

What

tar1090.adsb_upstreams is the ordered list of sources the tar1090 proxy tries until one answers, emitted to tar1090.env as ADSB_UPSTREAMS. It ships as "https://adsb.retina.fm,https://api.adsb.lol": RETINA's own service first, adsb.lol behind it.

Consumed by offworldlabs/tar1090-node#20.

Details

  • Both compose manifests must list the variable. The proxy reads it from its own environment, so a manifest that omits it leaves the proxy on its built-in default with no error anywhere. Verified against jonathan-node-1, whose running container carries only ADSBLOL_ENABLED and ADSBLOL_RADIUS today.
  • No migration. The key is new, so no deployed node has it in its first-boot copy of user.yml, and the shipped default reaches all of them. Changing this default later will need a migrate_*(), as the four existing ones do.
  • Written even when adsblol_fallback is off, so turning the fallback on later needs no second config change.

Testing

python -m unittest discover -s config-merger/test     # 61 pass

Two new cases: the chain reaching tar1090.env, and a config predating the key still producing a usable chain.

Also ran the real merger against the shipped default.yml with a node-shaped user.yml, which produces:

ADSBLOL_ENABLED=true
ADSBLOL_RADIUS=120
ADSB_UPSTREAMS=https://adsb.retina.fm,https://api.adsb.lol

Not verified

Nothing has run on hardware. Deploying needs a tar1090-node image carrying #20.

🤖 Generated with Claude Code

@Purple10101
Purple10101 force-pushed the feat/adsb-upstream-chain branch from f6519c9 to 191f4c3 Compare September 25, 2026 23:16
tar1090.adsb_upstreams is the ordered list of adsb.lol-format sources the
tar1090 proxy tries until one answers, emitted to tar1090.env as
ADSB_UPSTREAMS and consumed by offworldlabs/tar1090-node#20. It ships as
"https://adsb.retina.fm,https://api.adsb.lol": RETINA's own service first,
adsb.lol behind it.

Both compose manifests must list the variable. The proxy reads it from its
own environment, so a manifest that omits it leaves the proxy on its built-in
default with no error anywhere. Verified against jonathan-node-1, whose
running container carries only ADSBLOL_ENABLED and ADSBLOL_RADIUS today.

No migration. The key is new, so no deployed node has it in its first-boot
copy of user.yml and the shipped default reaches all of them. Changing this
default later will need a migrate_*(), as the four existing ones do.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@Purple10101
Purple10101 force-pushed the feat/adsb-upstream-chain branch from 191f4c3 to 7c218ef Compare September 25, 2026 23:29
@Purple10101 Purple10101 changed the title 20260922 - Let the ADS-B upstream chain be configured per node 20260926 - Point the tar1090 ADS-B fallback at adsb.retina.fm first Sep 25, 2026
@Purple10101
Purple10101 merged commit 2a5b687 into main Sep 27, 2026
1 check passed
@Purple10101
Purple10101 deleted the feat/adsb-upstream-chain branch September 27, 2026 08:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant