rcpagermachine

Pager

Rob has an old-school pager that he can receive messages on. Page him!

Best experienced on desktop
80 characters remaining

Architecture Diagram

What's going on under the hood?

Web/API laneRadio delivery lane1) Pager UI (/pager)User enters a message, clicks Send, and suppliesrccolamachine endpoint credentials.2) POST /api/pagerBrowser sends message text in the request body andendpoint credentials via Basic auth.3) Server GuardrailsServer validates credentials, enforces rate limits (1request / 3 seconds and 10 requests / minute per IP),and builds a normalized DAPNET payload.4) Upstream API call + fan-outServer posts to DAPNET using secure upstreamcredentials. After acceptance, it seeds status storageand prepares the browser response in parallel with radiodelivery.6) DAPNET network handoffDAPNET dispatches the message toward Rob's home networkpath.7) Home WiFi linkRob's Wi-Fi network receives the data and relays it toPi-Star MMDVM.8) Pi-Star radioPi-Star MMDVM turns the inbound message into a localRF/POCSAG transmission.5) API response to browserAPI returns ok/text/timestamp/trackingKey for statuspolling.11) PagerThe pager receives and displays the message over RF.10) DatabaseAccepted sends and telemetry stages are stored bytrackingKey.12) Status pollingBrowser polls GET /api/pager/status?trackingKey toupdate pager send status.9) Pi-Star telemetry bridgeBridge checks GET /api/pager/telemetry/active. If apending pager message exists, it posts relevant eventsto POST /api/pager/telemetry with trackingKey.