Say that retina-tracker also runs on every node - #30
Merged
Merged
Conversation
The architecture doc said retina-tracker is never deployed standalone and runs only inside the central server. Every node has run it as a sidecar in retina-node's compose for some time, and since node API 1.6.0 a node can send those tracks to the server, which can use them in place of its own in-process copy per node. A reader planning tracker work from this doc would miss half the deployments, and the half that is about to take over. Co-Authored-By: Claude Opus 5.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.
docs/architecture.mdsaid retina-tracker is never deployed standalone and runs only inside the central server. That has been wrong for some time: every node runs it as a sidecar in retina-node's compose, fed by blah2_api on loopback:30100.Since node API 1.6.0 (retina-server #563, #568, #570, #574), a node can send those tracks on the detection frame. The server can then use them in place of its in-process copy for that node, behind
NODE_TRACKS_MODE, which is off everywhere until the fleet cut-over.This PR changes:
The rest of §2 predates the v1 HTTPS node API and is not touched here.
🤖 Generated with Claude Code