feat(server): mint + expose a stable server_id (per-install identity) - #34
Merged
Conversation
The server had no durable identity, so a client could only key its per-server state on a random, device-local id that reset on remove/re-add or a URL change. Mint a stable server_id once (crypto/rand, URL-safe) into config.yaml so it survives a database rebuild, self-healing installs that predate it. Expose it in GET /server and in the pairing exchange / login / demo responses so a client can adopt it as the connection's identity the moment it pairs. Tests cover the mint-once/self-heal helper, config Save/Load persistence, and the /server + exchange wiring.
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.
The server had no durable identity, so a client could only key its per-server state on a random, device-local id that reset on remove/re-add or a URL change.
Mint a stable server_id once (crypto/rand, URL-safe) into config.yaml so it survives a database rebuild, self-healing installs that predate it. Expose it in GET /server and in the pairing exchange / login / demo responses so a client can adopt it as the connection's identity the moment it pairs. Tests cover the mint-once/self-heal helper, config Save/Load persistence, and the /server + exchange wiring.