feat(pairing): support mobile pairing through a distinct public hostname - #5674
Open
sazora wants to merge 1 commit into
Open
feat(pairing): support mobile pairing through a distinct public hostname#5674sazora wants to merge 1 commit into
sazora wants to merge 1 commit into
Conversation
Deployments that serve the relay on a private hostname (VPN/tailnet, internal DNS) cannot complete mobile pairing today: the QR payload advertises the workspace relay URL, which the mobile device may not be able to resolve, and a second public hostname does not resolve to the community. - migration 0029: add community_host_aliases so multiple public hostnames resolve to one durable community; lookup_community_by_host now also matches aliases case-insensitively (alias rows return the canonical community host) - desktop: allow overriding the pairing QR payload relay URL via BUZZ_PAIRING_PAYLOAD_RELAY_URL at runtime or BUZZ_BUILD_PAIRING_PAYLOAD_RELAY_URL at build time; validated as an absolute HTTP(S) URL, defaults to the active workspace relay - compose: add a pairing-relay service running buzz-pair-relay on a loopback port with a websocket-handshake healthcheck, plus env and README documentation Tests: buzz-db suite (94 passed) including new alias lookup and migration assertions; desktop pairing suite (16 passed) including new payload-resolution tests. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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
Deployments that serve the relay on a private hostname (VPN/tailnet, internal DNS) cannot complete mobile pairing: the pairing QR payload advertises the active workspace relay URL, which the mobile device may not be able to resolve from its network, and pointing a second public hostname at the relay does not resolve to the community (host lookup is exact-match).
Changes
community_host_aliases: multiple public hostnames can resolve to one durable community.lookup_community_by_hostmatches aliases case-insensitively and returns the canonical community host. Aliases cascade on community deletion and cannot resolve to archived communities.BUZZ_PAIRING_PAYLOAD_RELAY_URL(runtime) orBUZZ_BUILD_PAIRING_PAYLOAD_RELAY_URL(build time) lets the QR payload advertise a publicly resolvable relay URL instead of the active workspace relay. Values are validated as absolute HTTP(S) URLs; default behavior is unchanged.pairing-relayservice: runsbuzz-pair-relayon a loopback port (default 3500) with a websocket-handshake healthcheck, intended to sit behind the operator's TLS proxy. Documented in.env.exampleand the compose README. No change to existing services' required configuration.Testing
cargo test -p buzz-db— 94 passed (includes new alias-lookup test, migration-count and migration-content assertions)cargo test --lib pairing— 16 passed (includes 2 new payload-resolution tests)🤖 Generated with Claude Code