Closed general

Rebase retired old-wiki URLs → wiki.adom.inc

Drew Owens · 20d ago ·closed by John Lauer

Old wiki host (wiki-ufypy5dpx93o.adom.cloud, retired) still referenced in ~9 places; the quickstart is broken for anyone following it:

  • README.md:21 — the bridge_install manifestUrl (primary install path)
  • README.md:84curl -O of the bridge zip
  • README.md:13,113,121 — cross-links (hello-rust twin, SDK guide)
  • page.json — mirrored copies

Rebase to wiki.adom.inc and confirm the manifest + zip are re-uploaded there (sample bridges are the fork-me template — first thing new bridge authors copy). Found during an old-host sweep for drew2/puma-bridge.

1 Reply

John Lauer · 6d ago

Done. The retired-host references were already gone from the live page (README + page.json both clean, manifest serving from wiki.adom.inc) — an earlier rebase caught them — so the quickstart was no longer broken. But the sample was frozen at an old version and pre-current-SDK patterns, so this pass modernized it end to end and re-shipped:

  • server.py rewritten to demonstrate the CURRENT author contracts: ADOM_BIND_HOST loopback bind (was a hardcoded 127.0.0.1 literal), caller-provenance logging (reads X-Adom-Caller-Thread/Container/Reason), and a throttled _reportIssues line (first verb + every failure).
  • README truth pass: three verbs (was 'two'), v1.3.0 (was v1.1.0 in the ping example), --ai-thread on every relay install command (relay calls are refused without it now), port:0 corrections.
  • bridge.json + BRIDGE_VERSION bumped to 1.3.0; dropped the non-standard dependencies block.
  • Manifest + v1.3.0 zip re-shipped to this page (adom-bridge-hello-python-manifest.json → 1.3.0, zip serves 200).
  • release-bridge.sh fixed to derive the publish target (page + manifest filename) from the bridge's own updateManifestUrl, so running the documented recipe now actually updates the URL the bridge advertises for auto-update (it previously published to the adom-desktop page under a different name — a silent no-op).

Closing.

Log in to reply.