auto: docs sync 2026-07-14T12:00:21+00:00
Files changed: engine/.embcache.json engine/changelog.md engine/lint-report.md vault/docs/software/central.md
This commit is contained in:
parent
c45470095f
commit
3efdd560d5
4 changed files with 12 additions and 6 deletions
|
|
@ -5,12 +5,12 @@ tags:
|
|||
- mesh
|
||||
aliases: []
|
||||
related:
|
||||
- [[navi]]
|
||||
- [[central-deploy-cutover]]
|
||||
- [[services]]
|
||||
- [[navi]]
|
||||
- [[fleet-platform-baseline]]
|
||||
- [[caddy]]
|
||||
updated: 2026-07-13
|
||||
updated: 2026-07-14
|
||||
---
|
||||
# central — Data-Hub Spine
|
||||
|
||||
|
|
@ -35,7 +35,7 @@ central is a multi-domain real-time data-hub spine. Adapters normalize upstream
|
|||
|
||||
## Architecture
|
||||
|
||||
The data flow is: upstream APIs → adapters (central-supervisor) → NATS/JetStream :4222 → central-archive (TimescaleDB/PostGIS :5432). The central-gui (FastAPI + HTMX, :8000) exposes the API consumed by navi via recon-vm's nginx (port 8440, `^~ /api/traffic/` → `central.echo6.mesh:8000`).
|
||||
The data flow is: upstream APIs → adapters (central-supervisor) → NATS/JetStream :4222 → central-archive (TimescaleDB/PostGIS :5432). The central-gui (FastAPI + HTMX, :8000) exposes the API consumed by [[navi]] via recon-vm's nginx (port 8440, `^~ /api/traffic/` → `central.echo6.mesh:8000`).
|
||||
|
||||
## Systemd Services
|
||||
|
||||
|
|
@ -101,7 +101,7 @@ Single TimescaleDB hypertable `public.events` (~40 GB, ~3.42 M rows, 331 chunks,
|
|||
## Deploy / State Notes (as of 2026-07-13)
|
||||
|
||||
- **Deployed HEAD:** v0.15.0 (detached HEAD — the box tracks tags; sha `3c8da28`, `pyproject.toml` 0.15.0). All 3 units active, `/health` 200, 23 adapters configured / 22 enabled (only `n2yo_visualpasses` disabled).
|
||||
- **v0.15.0 (deployed 2026-07-02, PRs #120–124):** the GUI can now add public REST/GeoJSON data sources **no-code** — a generic adapter kind created and configured entirely through adapter management, no repo change. None enabled in this deployment yet; all 23 current adapters remain bespoke per-source kinds (each `config.adapters.kind` is unique to its source).
|
||||
- **v0.15.0 (deployed 2026-07-02, PRs #120–124):** the GUI can now add public REST/GeoJSON data sources **no-code** — a generic adapter kind created and configured entirely through adapter management, no repo change. None enabled in this [[deployment]] yet; all 23 current adapters remain bespoke per-source kinds (each `config.adapters.kind` is unique to its source).
|
||||
- **Deploy mechanism:** manual, tag-based (`git checkout <tag>` → `uv sync` → `central-migrate` → restart). One-command `scripts/deploy.sh` ships in-repo; full procedure in the [[central-deploy-cutover]] runbook. No CI/CD; no automated DB backup (pre-flight `pg_dump` is the only migration safety net; migrations are forward-only).
|
||||
- **`central-migrate` env gotcha:** manual calls need `cd /opt/central && set -a && . /etc/central/central.env && set +a && …` (the units supply this via WorkingDirectory + EnvironmentFile).
|
||||
- **EONET:** now **global** as of v0.14.6 (2026-06-28) — `bypass_bbox_filter=True` + the adapter `region` key removed. NOTE: its `events`-table row count is a misleading health signal (dedup + partition expiry); use the CENTRAL_DISASTER stream as the EONET flow signal. `avalanche_org` zero-events is expected (off-season gate).
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue