Repository navigation
Conversation
mwolson
force-pushed
the
personal/background-relay-service
branch
from
October 22, 2026 03:11
061d0a4 to
9ad2ab2
Compare
mwolson
force-pushed
the
personal/background-relay-service
branch
from
October 22, 2026 04:53
9ad2ab2 to
685f93e
Compare
mwolson
force-pushed
the
personal/background-relay-service
branch
from
October 23, 2026 23:19
685f93e to
a39c464
Compare
mwolson
force-pushed
the
personal/background-relay-service
branch
from
October 24, 2026 00:11
a39c464 to
8f9fa47
Compare
mwolson
force-pushed
the
personal/background-relay-service
branch
from
October 24, 2026 00:38
8f9fa47 to
0851ae6
Compare
mwolson
force-pushed
the
personal/background-relay-service
branch
from
October 24, 2026 01:36
0851ae6 to
7400dd7
Compare
mwolson
force-pushed
the
personal/background-relay-service
branch
2 times, most recently
from
October 24, 2026 19:49
e53355f to
f351ff0
Compare
mwolson
force-pushed
the
personal/background-relay-service
branch
from
October 29, 2026 11:33
f351ff0 to
8b37820
Compare
mwolson
force-pushed
the
personal/background-relay-service
branch
from
October 29, 2026 13:24
8b37820 to
39eeaf6
Compare
mwolson
force-pushed
the
personal/background-relay-service
branch
from
October 30, 2026 00:23
39eeaf6 to
063ee50
Compare
mwolson
force-pushed
the
personal/background-relay-service
branch
from
November 10, 2026 03:11
c3cfcfc to
9a85b52
Compare
mwolson
force-pushed
the
personal/background-relay-service
branch
from
November 10, 2026 06:59
9a85b52 to
26a6900
Compare
mwolson
force-pushed
the
personal/background-relay-service
branch
from
November 10, 2026 07:34
26a6900 to
1107788
Compare
mwolson
force-pushed
the
personal/background-relay-service
branch
from
November 10, 2026 14:59
1107788 to
c9f6dd5
Compare
mwolson
force-pushed
the
personal/background-relay-service
branch
from
November 10, 2026 16:19
c9f6dd5 to
8c1a3fd
Compare
mwolson
force-pushed
the
personal/background-relay-service
branch
from
November 10, 2026 21:17
8c1a3fd to
36f68e5
Compare
mwolson
force-pushed
the
personal/background-relay-service
branch
from
November 11, 2026 23:29
36f68e5 to
c994e49
Compare
Add a background-only APNs relay on Node 26.12.1 with Postgres for Mike's personal iOS build, served at t3-relay.mikemail.work. Environment enrollment and a separate admin CLI keep bootstrap and diagnostics out of the public HTTP API. Derive completion eligibility from durable server events and persist the publish sequence across restarts, so held completions can alert when released while retries retain their transition identity and ordering. This layer is fork-only. It reuses the hosted relay's runtime services and supplies its own account worker, delivery ledger and Node HTTP/2 transport. Local tests generate their TLS keys and certificates at runtime.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
T3's hosted relay signs APNs requests with T3 Tools' key, so it cannot reach my personally signed iOS build (
com.mwolson.t3code.v2.dev). Push notifications and Live Activities for that build need a relay that holds my own key.Change
Adds
infra/personal-relay, a background-only APNs relay for my personal iOS build, served att3-relay.mikemail.work. It runs on Node 26.12.1 with Postgres. It accepts device and Live Activity registrations from my T3 sign-in (Clerk JWKS pinned to my account, then DPoP) and signed activity publishes from enrolled environments. A separate admin CLI enrolls environments with a proof from each host and lists or revokes them; enrollment is not part of the public HTTP API. Delivery uses a Postgres alert ledger with per-device and per-channel retries, device backfill on registration and bounded APNs payloads, sent over Node HTTP/2. The relay reuses the hosted relay's runtime services and supplies its own account worker, delivery ledger and transport.On the server side, completion alerts take their eligibility time from durable orchestration events, so a completion held by background work, monitors, a monitor holding a background wake, or PR watches alerts when the hold releases. The publish sequence survives restarts, so retries keep their transition identity and order.
T3 Connect discovery, connections and tunnels stay on
relay.t3.codes. Deployment manifests and sealed secrets live in my webserver repo, not here.Scope
Personal layer, fork-only. It exists for my own signing setup and will never be proposed upstream.
Verification
Run on zbook26. Focused tests at the layer pass: 59 server, 1 shared, 1 relay-queue and 67 personal-relay tests, plus 19 database tests across six files against a throwaway PostgreSQL 17 container. With the production change reverted, the public enrollment-proof command test and the signed durable attention-request identity and time test fail. The long-held completion table gains a
monitor_wakerow, which fails without the monitor wake hold (eligibility stays at 15 minutes instead of the monitor's release at 20 minutes 5 seconds); the completion-eligibility and relay files pass all 42 tests with it.No relay image was built, pushed or deployed for this version, and no deployed relay or phone was contacted.
Known Limitations
The relay image and its README pin
node:26.12.1-alpine, while the repository's engine is now Node 26.13.1, so the bundle built with the newer toolchain runs on the older patch release until the image is moved up.