Files

T

fkrebs 143343decf docs: session continuity file + claude-max-bridge /v1/responses fix

- Add RESUME.md for cross-session continuity (open items, key state, constraints)
- claude-max-bridge: implement /v1/responses (OpenAI Responses API) with
  previous_response_id chaining via server-side history injection into system prompt.
  Root cause of "session already in use": CLI leaves JSONL in un-resumable
  "dequeued" state after each --print run; fix avoids session reuse entirely.
  Also fixed: assistant content must be array-of-blocks not plain string (silent
  JS crash otherwise).
- LiteLLM: add pass_through_endpoints for /v1/responses → claude-max-bridge
- Storage, volumes, architecture docs reconciled (Vaultwarden → local zfs,
  Pocket-ID backup, WAL-G fix, apps/ decommission, Nextcloud CIFS→NFS)
- Add ideas/, proxmox-memory-audit.md, llm-benchmark.md (new docs this session)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-05-22 22:42:17 +02:00

3.9 KiB

Raw Blame History

CT / VM inventory

Verified 2026-05-20 via pct list, pct config <id>, qm config 100 on nuc.

VMID	Name	Type	IP	Cores	RAM (MiB)	Rootfs	Role	UNAS mount	GPU	Status
100	haos	VM (q35/OVMF)	DHCP via vmbr0 (`.60`)	4	16384 (balloon 4096)	32 GiB local-zfs	Home Assistant OS; USB Zigbee dongle (10c4:ea60) passed through	—	no	running
101	shepard	LXC unpriv	192.168.1.49/24	12	32768	500 GiB	Shepard product stack (Caddy, frontend, backend, Keycloak, Mongo, Neo4j, TimescaleDB)	mp0 NFS	Intel iGPU (card+render)	running
102	dns	LXC unpriv	192.168.1.2/24	2	1024	4 GiB	AdGuard Home — LAN DNS resolver + filter	—	no	running
103	backrest	LXC unpriv	192.168.1.3/24	1	512	8 GiB	Backrest (restic) backup scheduler	mp0 NFS	no	running
104	docker	LXC unpriv (idmapped)	192.168.1.40/24	16	49152	200 GiB	Main Docker host — AI/ML + media + identity-adjacent (~65 containers)	mp0 NFS	Intel iGPU (card+render)	running
105	nextcloud	LXC priv	192.168.1.41/24	4	8196	100 GiB	Nextcloud AIO	mp0 NFS	Intel iGPU (render only)	running
108	zoraxy	LXC unpriv	192.168.1.4/24	2	2048	6 GiB	Zoraxy reverse proxy + ACME (`*.nuclide.systems`)	—	no	running
109	ops	LXC	⚠️ TBD (`.6`=CT 113, `.7`=CT 112) — likely `.8`	4	8192	50 GiB	Planned — Prometheus, Loki, Grafana, Arcane Manager, Dozzle, Homarr, Diun, sshwifty, Tinyauth, socket-proxy; Alloy agents on all hosts	—	no	planned (see `infra/proxmox-state.md` §16)
110	id	LXC unpriv	192.168.1.5/24	1	1024	4 GiB	Pocket-ID OIDC IdP (`id.nuclide.systems`); migrated off CT 104 on 2026-05-20	—	no	running
111	dev	LXC unpriv	192.168.1.42/24	12	32768	60 GiB	Dev host — Coder + Gitea + workspaces	mp0 NFS	Intel iGPU (render only; symlinked at `/dev/dri/renderD128`)	running
112	secrets	LXC unpriv	192.168.1.7/24	2	4096	20 GiB	Infisical secrets manager (own Postgres 16 + Redis 7; replaces scattered .env files) — LAN-only, no Zoraxy route	—	no	running
113	db	LXC unpriv	192.168.1.6/24	2	4096	40 GiB	Shared Postgres 17 + pgAdmin + WAL-G → Garage S3; Arcane edge agent	—	no	running

UNAS NFS = 192.168.1.31:/var/nfs/shared/storage over NFSv3. CT 105 (Nextcloud) is the lone outlier — it mounts the same UNAS share over CIFS/SMB 3.1.1, not NFS.

CT 112 ("secrets") — Infisical deployed 2026-05-22; see services/secrets-manager.md. LAN: http://192.168.1.7:8200. No Zoraxy route — secrets must not be internet-exposed.

CT 105 ("nextcloud") — migrated from CIFS (//192.168.1.31/storage) to NFS (192.168.1.31:/var/nfs/shared/storage) on 2026-05-22. CIFS mount was not remounting after host reboots, causing Nextcloud crash-loops. NFS is consistent with all other CTs.

SSH access

The Proxmox host (nuc, 192.168.1.20) has root SSH access to all LXC containers via key auth. To grant your own key access to every running container in one step, run on the host:

deploy-ssh-key "ssh-ed25519 AAAA... you@yourmachine"
# or pipe it:
ssh nuc 'cat' < ~/.ssh/id_ed25519.pub | deploy-ssh-key

Script is at /usr/local/bin/deploy-ssh-key. It iterates pct list, skips stopped CTs, and appends the key to /root/.ssh/authorized_keys idempotently (no duplicates).

VM 100 (HAOS, 192.168.1.60) cannot be reached via pct exec. Install manually in the HA terminal:

echo "ssh-ed25519 AAAA... you@yourmachine" >> ~/.ssh/authorized_keys

Host key (root@nuc, already deployed to all CTs 2026-05-21):

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQCuVqBW3VXg... root@nuc

CT 113 ("db") provisioned 2026-05-21; see services/databases.md. Future role: consolidate per-stack Postgres instances once second NVMe lands.

3.9 KiB Raw Blame History

CT / VM inventory

SSH access

3.9 KiB

Raw Blame History