admin/bf-infra
1
0
Fork 0
Code Issues 21 Pull Requests Actions Packages Projects Releases Wiki Activity
61 Commits 5 Branches 0 Tags
c51704fd8463c72e335962b4a5626943fe5b10a9
Commit Graph

3 Commits

Author SHA1 Message Date
Christoph Emsenhuber
6dea5ec361 docs 📄 cf-tunnel §8: Ingress v116 (.41→.20) + Connector-Reachability nach NAS-VLAN20-Cutover 
- 6 NAS-Origins .41→.20 repointet (ha-mcp, NAS-ssh, gitea, vw, grafana, pve-mcp), v115→v116.
- Befund: pve-Connector erreicht VLAN20 (vw 200 via Tunnel); 502 direkt nach Ingress-PUT = transient.
- grafana 502 = Container exited, kein Routing-Problem. Kein pve-Static-Route nötig.
- Stufe-4-Connector-Vantage löst sich mit pve→VLAN20 (PVID1-Cutoff).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
 2026-07-10 09:42:33 +02:00
Christoph Emsenhuber
6807c5da08 CF/#1033 ✅ Track A komplett: bf-Tunnel pve-only + Ingress-Repoints + DNS-Cleanup 
- A1: n8n Compose-Port .41.167→.20.167 (Daten/Encryption-Key erhalten), NAS-Leichen weg
- A2: Ingress v106 alle Origins .41.167→.20.167, hermes-geli neu, mcp-ms365 raus
- A3: hermes-geli-CNAME + 12 tote/Orphan-CNAMEs gelöscht
- Endzustand: Tunnel healthy/1 Connector, 23 Ingress↔23 CNAMEs, keine Waisen
- Zugang via scoped API-Token (mcp/cloudflare/.env), OAuth-MCP blieb read-only

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
 2026-07-02 09:21:27 +02:00
Christoph Emsenhuber
381365b8ed CF/#1033 📄 CF-Tunnel-Mapping (SSoT) + cloudflare-MCP-Scaffold 
- docs/cf-tunnel-mapping.md: Single Source of Truth zur #1033-Diagnose
  (bf-Tunnel = Round-Robin über 3 Connectors macmini/pve/NAS)
- mcp/cloudflare/: README + .env.example (echtes .env via mcp/.gitignore ausgeschlossen)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
 2026-07-01 17:49:46 +02:00