fix(cloudflared): kreisel.mana.how + kreisel-api.mana.how Ingress nachziehen
Some checks are pending
CD Mac Mini / Detect Changes (push) Waiting to run
CD Mac Mini / Deploy (push) Blocked by required conditions
CI / Detect Changes (push) Waiting to run
CI / Validate (push) Waiting to run
CI / Build mana-search (push) Blocked by required conditions
CI / Build mana-sync (push) Blocked by required conditions
CI / Build mana-api-gateway (push) Blocked by required conditions
CI / Build mana-crawler (push) Blocked by required conditions
Mirror to Forgejo / Push to Forgejo (push) Waiting to run

Beim 2026-05-20-Cutover war Schritt "Ingress in cloudflared-config.yml" zwar
im Memory abgehakt, aber nie wirklich gemacht — beide Hosts liefen in den
service: http_status:404 Catchall. App-Symptom: Native zeigte "API-Fehler
404:" in Töpfe-/Aufnehmen-Tab, Container kreisel-api selbst war healthy.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Till JS 2026-05-20 16:15:44 +02:00
parent f2803fab0e
commit 767c3b7970

View file

@ -434,4 +434,12 @@ ingress:
- hostname: hub.mana.how
service: http://localhost:3082
# Kreisel — Loop-Video-App für Verein-Töpfe (Code/kreisel/).
# Container manacore-monorepo, Host-Ports 3115 api / 3116 web
# (PORTS.md). Live seit 2026-05-20, invite-only via mana-auth-tier.
- hostname: kreisel.mana.how
service: http://localhost:3116
- hostname: kreisel-api.mana.how
service: http://localhost:3115
- service: http_status:404