mirror of
https://github.com/n30nex/CartoLite-Server.git
synced 2026-10-17 11:29:58 +00:00
* Bring CartoLite visuals and recovery to the worldwide server with Netgraph * Remove remaining country-overlay cleanup references * Align the CI container identity with the integration checks * Exercise worldwide grid areas in the large-topology benchmark
1.3 KiB
1.3 KiB
CartoLite Server agent instructions
Purpose
CartoLite Server is a compact worldwide MeshCore map and Netgraph: a Go MQTT/HTTP process, a vanilla TypeScript/MapLibre client, transient Canvas animation, and one atomic checkpoint. Keep it suitable for independent self-hosting. Netgraph areas use coordinate-derived global grid squares, never country-specific lists.
Boundaries
- Never expose public keys, observer keys, raw path hex, packet hashes, packet payloads, decoded message text, credentials, or resolver reasons.
- Never infer ambiguous, non-forwarder, missing-coordinate, missing-RF, or distance-gated route hops.
- Keep public API schema v2 synchronized between Go and TypeScript.
- Do not add analytics, accounts, chat, packet history, SQLite, an Android app, country-specific data, or Labs.
- Use synthetic fixtures only. Never commit live broker data,
.env, checkpoints, captures, or secret files.
Delivery
- Preserve the scratch, non-root, read-only, capability-free container.
- Supply browser basemap credentials only through a BuildKit secret.
- Keep
REGION_ALLOWLISToptional and exact when configured. - Run frontend tests/build, Go tests/vet/race, integration/privacy smoke tests, and
git diff --checkbefore release. - Preserve unrelated work and never force-push shared branches.