2c5894d70b
services/kb-site/ — nginx:alpine serwujacy wolumen kb-site_content (:ro, /usr/share/nginx/html), pelny layout z CLAUDE.md: docker-compose.yml, service.yaml, README-wskaznik, env.example (swiadomie pusty — brak sekretow), healthcheck.sh. Wpis w hosts/piha/services.yaml. Port hosta 8250, NIE 8240 z opisu zadania: 8240 jest juz zajete przez narty27 (services/narty27/docker-compose.yml). Blok statyczny PIHA to 8210 paperless, 8220 nextcloud, 8230 kb-query, 8240 narty27 -> 8250 to nastepny wolny. Uzgodnione z operatorem. exposure: public — w odroznieniu od narty27 ta wystawka ma byc dostepna z internetu przez vhost npm@PIHA kb.okit.pl; bind :8250 jest upstreamem proxy, nie punktem wejscia. Tresc jest czystym artefaktem repo (wyjscie scripts/kb/gen_pages.py), zyje wylacznie w wolumenie kb-site_kb-site_content — bez binda pod /opt/homelab/data i bez zadania backupu: odtworzeniem jest regeneracja z kb/. Sprawdzone lokalnie: docker compose config -q, bash -n healthcheck.sh, yaml.safe_load na obu manifestach. |
||
|---|---|---|
| .claude/skills | ||
| backups/zigbee | ||
| docs/sessions | ||
| dotfiles | ||
| hardware/esp/ir-ac-ha-integration | ||
| hosts | ||
| inventory | ||
| jobs | ||
| kb | ||
| packages | ||
| scripts | ||
| services | ||
| .codex | ||
| .gitignore | ||
| .mcp.json | ||
| CLAUDE.md | ||
| codex_context | ||
| codex_context.yaml | ||
| deploy_agent.py | ||
| ollama_client.py | ||
| README.md | ||
| start-aider.sh | ||
| start-codex.sh | ||
| sync-context.sh | ||
| update-context.md | ||
Homelab Codex
GitOps-lite orchestration for a distributed homelab environment.
Architecture
The homelab consists of several nodes connected via a Tailscale internal mesh.
| Host | Role | Description |
|---|---|---|
| SATURN | Primary Node | Development, orchestration, and git source of truth (commit node). |
| SOLARIA | Compute Node | GPU, inference, and heavy compute workloads. |
| PIHA | Infra Node | Core infrastructure services, automation, and monitoring. |
| VPS | Edge Node | Public ingress, reverse proxy, and edge services. |
Agent System
The homelab uses a multi-agent orchestration model with human-in-the-loop for destructive actions:
| Agent | Node | Role |
|---|---|---|
| stability-agent | all nodes | Per-node watchdog — monitors Docker, disk, Tailscale, MQTT; emits events |
| node-agent | all nodes | Publishes container health events to Redis pub/sub |
| observer | VPS | Synthesizes world state from events into /opt/homelab/world/*.json |
| supervisor | VPS | Detects drift between desired and actual state; writes pending actions |
| planner-agent | SOLARIA | LLM-powered diagnosis — listens to Redis, proposes remediation actions |
| executor | VPS | Executes actions only after operator approval |
| operator-ui + telegram-bot | VPS / PIHA | Operator reviews and approves/rejects pending actions |
Action approval flow: pending/ → operator approves → approved/ → executor runs.
Repository Structure
docs/: Infrastructure Standards and Deployment Conventions.kb/phases/subsystem-a-naprawa.md: Current Maintenance Plan (Control Plane).hosts/: Host-specific configurations and service assignments.services/: Reusable Docker Compose service definitions.scripts/: Deployment and management scripts.
Getting Started
- Standardization: Follow the Infrastructure Standards.
- Deployment: See Deployment Conventions for how to roll out changes.
- SATURN: Remember that SATURN is the only node where commits should be made.
Documentation Index
- Current Maintenance Plan (Control Plane)
- Infrastructure Standards
- Agent Operating Procedures (For AI/Non-Human Agents)
- Deployment Conventions
- Hardware
- Networking
- Services
- Node Capabilities
- Action Model
Note: This repository documents the state of the homelab. Runtime state lives outside the repository in /opt/homelab.