eSlider/swarm-house
1
0
Fork 0
Code Issues 2 Pull Requests 3 Actions Packages Projects 1 Releases 13 Wiki Activity

docs: live demo external links in design journey #3

Open
eSlider wants to merge 2 commits from docs/live-demo-links into main
pull from: docs/live-demo-links
merge into: :main
Conversation 0 Commits 2 Files Changed 2
+23 -4
2 changed files with 23 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/release.yaml
+8 -4
View File
@@ -24,8 +24,10 @@ jobs:
steps:
- name: Checkout
run: |
git clone --depth=50 https://${{ gitea.actor }}:${{ gitea.token }}@git.produktor.io/${{ gitea.repository }}.git .
git checkout ${{ gitea.sha }}
git init .
git remote add origin https://${{ gitea.actor }}:${{ gitea.token }}@git.produktor.io/${{ gitea.repository }}.git
git fetch --depth=50 origin "${{ gitea.ref }}"
git checkout FETCH_HEAD
- name: Install dependencies
run: pip install --quiet -r simulator/requirements.txt
@@ -61,8 +63,10 @@ jobs:
steps:
- name: Checkout
run: |
git clone --depth=1 https://${{ gitea.actor }}:${{ gitea.token }}@git.produktor.io/${{ gitea.repository }}.git .
git checkout ${{ gitea.sha }}
git init .
git remote add origin https://${{ gitea.actor }}:${{ gitea.token }}@git.produktor.io/${{ gitea.repository }}.git
git fetch --depth=1 origin "${{ gitea.ref }}"
git checkout FETCH_HEAD
- name: Install Trivy
run: |
docs/12-design-journey.md
+15
View File
@@ -129,6 +129,13 @@ coming back to foundations DevOps and sysadmins already trust.
> - [`simulator/explorer/server.py`](https://git.produktor.io/eSlider/swarm-house/src/branch/main/simulator/explorer/server.py#L111-L131) — the query path a peer or an engineer hits identically
> - [`simulator/tests/test_sql_gate.py`](https://git.produktor.io/eSlider/swarm-house/src/branch/main/simulator/tests/test_sql_gate.py#L13-L35) — the gate is safety-critical, so it is tested first
The explorer is running, not just described: the data-plane view (partition tree
and read-only SQL console) is live at
[swarm-data-explorer.produktor.io](https://swarm-data-explorer.produktor.io/)
(same access as this repository and [swarm.produktor.io](https://swarm.produktor.io/)).
Browse the Hive layout, run `SELECT` queries against the live lake, and see the
same statement gate a peer drone would hit in flight.
## 8. Replication and offload
Moving accumulated data uses rsync-class tooling (rclone) over the same SSH
@@ -170,6 +177,14 @@ scanning the whole lake on every query does not scale, so the scan is
> - [`simulator/monitoring/grafana/dashboards/`](https://git.produktor.io/eSlider/swarm-house/src/branch/main/simulator/monitoring/grafana/dashboards) — the fleet and platform dashboards
> - [`.github/workflows/release.yaml`](https://git.produktor.io/eSlider/swarm-house/src/branch/main/.github/workflows/release.yaml) — tests, smoke flight, Trivy, semantic release
The dashboard is running, not just described: **Swarm Fleet — generated data** is
live at
[swarm-analalytics.produktor.io](https://swarm-analalytics.produktor.io/d/swarm-fleet/swarm-fleet-e28094-generated-data?orgId=1&refresh=5s)
(same access as this repository, [swarm.produktor.io](https://swarm.produktor.io/),
and [swarm-data-explorer.produktor.io](https://swarm-data-explorer.produktor.io/)).
Telemetry rows, detections, pose frames, battery, and link quality — all derived
from the Parquet lake via SQL, not from agents on the drones.
## 10. Working method
A note on how this is meant to be built, not just what. Working together needs a