Repository navigation
Conversation
This was referenced Oct 21, 2026
Draft
Draft
Add optional attributed repeater telemetry and availability filtering
MeshCore-Beacon/beacon-web#184
Draft
This was referenced Oct 23, 2026
Open
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.
Consolidate Beacon's project roadmap, release-candidate qualification and operator handoff against the current repositories and running environments. The roadmap inventories all 25 pre-existing open issues and 34 open PRs, separates the primary core and optional telemetry lanes, identifies superseded work, and defines the staged acceptance path to live. Tracking: #45.
The review includes fresh read-only live/dev/dev1/Canadaverse checks. Live still reproduces four large-cursor errors; dev is on schema 053; dev1 is stopped; the preview's shared-host I/O pressure remains a performance gate. The Topology follow-up is now on the core/optional candidates and the exact preview pair, with native checks, query parity and public artifact/API proof. The report distinguishes those results from production-scale, browser/device and overnight qualification that remain open.
Also resolve the deployment-template portion of #13: add one bounded
json-filepolicy (max-size: 10m,max-file: 3) to all 11 services in the three supplied templates. A parsed before/after comparison confirms that only logging changed. Existing containers require a planned recreation; no runtime deployment, data-volume or secret change is made by these templates. Caddy access logs and database/WAL/backup retention remain separate responsibilities.Correct the contributing guide's stale three-repository list and disabled-docs-issues statement. Canonical mobile development belongs in beacon-flutter-app; old archive/scratch/fork lanes are explicitly classified in the roadmap.
This PR remains draft and targets dev. It contains documentation and deployment-template settings, not approval to merge or deploy application code. The matching optional documentation remains #44. No reviewer request or production write was made.