Repository navigation
Conversation
Owner
Author
|
Review feedback addressed (commit
Full Docker image validation was unavailable locally because the Docker daemon is not running. This change touches only two Dockerfile lines; it introduces no application or UI logic. CI will rerun the canonical COPY invariant check and remaining checks. |
Owner
Author
|
Closing per owner decision (2026-10-14): we will not maintain an admin-curated infrastructure list for now. The branch is kept, so the work can be revived later if that changes. |
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.
Adds an Infrastructure page inspired by the NashMesh Infrastructure page and its frontend implementation, adapted to our architecture. It has an admin-curated repeater set and a separate, activity-ranked shortlist of candidate repeaters. Suggestions are never auto-selected. The public page shows selected repeaters on a map with their current relay and bridge metrics.
Admin Select/Remove decisions use an authenticated, bounded file queue; only the ingestor writes the curated set into the main SQLite database, so it is included in the normal backup/restore lifecycle. Both server and ingestor validate that selected keys are known repeaters. The UI verifies the API key before showing controls, confirms each action, and keeps the key in memory only.
Validation: full server and ingestor Go suites; dbschema suite;
sh test-all.sh(235/235); targeted Chromium desktop/mobile flow including wrong-key gating, explicit Select/Remove, and no mobile overflow. No deployment.This PR is independent of #375 and #376.