docs: clarify peer onboarding is contribute-only + invite-first ordering#28
Merged
Merged
Conversation
Two clarifications driven by a real peer's onboarding session: - State plainly the connection is contribute-only -- peers upload, they do NOT query the shared graph; the query endpoints aren't exposed to peers. Heads off the confusion of a peer who was told "you can query" hitting a 404 on /cypher. - Make the accept-the-invite-first ordering explicit: confirm the shared machine appears in Tailscale before testing; a curl 000 means the share isn't active yet, not a server fault (the most common first-run snag). No real server names -- generic placeholders only. Generated with [Amplifier](https://github.com/microsoft/amplifier) Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.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.
Two clarifications from a real peer onboarding session:
State plainly the connection is contribute-only: peers upload their sessions, they do NOT query the shared graph. The query endpoints (/cypher) are not exposed to peers — heads off confusion when a peer is told 'you can query' and hits a 404.
Make the accept-the-invite-first ordering explicit: confirm the shared machine appears in Tailscale before testing connectivity. A curl 000 means the share isn't active yet, not a server fault — the most common first-run snag.
No real server names — generic placeholders only.