matt/echo6-docs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

auto: docs sync 2026-04-19T06:00:07+00:00

Browse source 
Files changed: docs/hardware/environment.md docs/services/services.md runbooks/recon-operations.md runbooks/recon-service-integration.md
This commit is contained in:
echo6-autocommit 2026-04-19 06:00:07 +00:00
commit 19ff1c7e79
4 changed files with 36 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

8
runbooks/recon-service-integration.md
View file

@ -8,7 +8,7 @@ Use this when you have a service running on a remote LXC/VM that needs a web man
## Prerequisites
- A running Flask or FastAPI dashboard (e.g., RECON on CT 130, WATCHTOWER on Contabo)
- A running Flask or FastAPI dashboard (e.g., RECON on VM 131, WATCHTOWER on Contabo)
- The target service running on a reachable host (LXC, VM, or bare metal)
- SSH access from the dashboard host to the target host
- The dashboard runs as a known user (e.g., `zvx`, `recon`, `watchtower`)
@ -421,7 +421,7 @@ lines = min(lines, 500) # Cap to prevent abuse
### RECON managing pipeline services (CT 130 dashboard → CT 110 PeerTube)
```
DASHBOARD_HOST=192.168.1.130 (CT 130, data node)
DASHBOARD_HOST=192.168.1.130 (VM 131, data node)
DASHBOARD_USER=zvx
TARGET_HOST=192.168.1.170 (CT 110, media node)
SERVICE_NAME=peertube
@ -453,7 +453,7 @@ Services managed:
- pt-downloader (CT 110): start/stop/restart/status/logs
- pt-importer (CT 110): start/stop/restart/status/logs
- pt-transcoder (cortex): start/stop/restart/status/logs
- recon (CT 130): start/stop/restart/status/logs
- recon (VM 131): start/stop/restart/status/logs
Each service has its own sudoers file on its target host,
its own entry in SERVICE_INTEGRATIONS, and its own UI panel.
@ -461,4 +461,4 @@ its own entry in SERVICE_INTEGRATIONS, and its own UI panel.
---
*Last updated: 2026-02-17*
*Last updated: 2026-04-19 — Updated CT 130 references to VM 131*