2026-07-22 17:29:11 +02:00
|
|
|
# Copy to .env next to docker-compose.yml (gitignored); docker compose picks
|
|
|
|
|
# it up automatically. Same convention as services/fleet-prometheus,
|
chore(vps): remove gokapi (operator decision 2026-08-26)
gokapi was VPS desired state (hosts/vps/services.yaml) with no matching
runtime on the node — a real deployment gap left open at the end of the
2026-08-26 recon session ("redeploy-vps-gokapi pozostawiony — realna
luka wdrożeniowa", docs/sessions/2026-08-26.md). Operator decision this
session: drop it instead of deploying it. Verified zero footprint on
VPS: no data, no container, no image, no /opt/homelab/config/gokapi.
Removed the desired-state entry from hosts/vps/services.yaml and the
services/gokapi/ compose stack. No hosts/vps/runtime/gokapi override
existed to remove.
Grepped the repo for dangling references: jobs/deploy-runner/tests and
services/control-plane/tests use "gokapi" only as an arbitrary example
service name in synthetic tmp_path fixtures (not reading the real
services/gokapi/ directory) — unaffected, left as-is. Fixed one stale
mention in services/control-plane/env.example's example-services
comment. kb/ and docs/sessions/ mentions (service doc, cutover
runbook, an open backlog item, prior session logs) are historical/
narrative record, not code or active config — left untouched, out of
this task's scope; flagged as a follow-up below.
Full control-plane (183), node-agent (70), and deploy-runner (44) test
suites pass unchanged.
Follow-up (not done here — kb/ editing is out of scope for this
worktree task): kb/decisions/backlog-aktywne.md still has an open
"gokapi: deploy-node VPS rzuca błąd — brakujący .env" entry that is now
moot and should be closed/removed.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017WDKj5LRY8vdQMx57dfNnu
2026-08-26 21:09:46 +02:00
|
|
|
# services/llm-gateway, services/ollama.
|
2026-07-22 17:29:11 +02:00
|
|
|
|
|
|
|
|
# Tailscale IP of the VPS node. The operator-ui port (18180) is published as
|
|
|
|
|
# ${TAILSCALE_BIND_IP}:18180:8080 so the mesh-facing bind is never 0.0.0.0.
|
|
|
|
|
# Verify when rebuilding the host: tailscale ip -4.
|
|
|
|
|
#
|
|
|
|
|
# WARNING (same footgun as fleet-prometheus, see its README): if .env is
|
|
|
|
|
# missing at deploy time, Compose resolves this to an empty string and
|
|
|
|
|
# SILENTLY binds to 0.0.0.0 instead of failing — always confirm with
|
|
|
|
|
# `docker compose config | grep host_ip` before `up -d`.
|
|
|
|
|
TAILSCALE_BIND_IP=100.95.58.48
|