feat(infra): community.mana.how (instead of analytics.*) for the public-feedback hub

analytics.mana.how DNS already existed as a non-CNAME record — picking
the user-facing 'community.mana.how' subdomain instead. Added the
tunnel ingress + matched the CORS origin + client-side env var.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Till JS 2026-04-27 01:00:22 +02:00
parent 515de79c8b
commit cabfd1004d
2 changed files with 3 additions and 3 deletions

View file

@ -148,7 +148,7 @@ ingress:
service: http://localhost:3065
- hostname: research.mana.how
service: http://localhost:3068
- hostname: analytics.mana.how
- hostname: community.mana.how
service: http://localhost:3064
# ============================================

View file

@ -587,7 +587,7 @@ services:
# ("Wachsame Eule #4528"). Set in .env.macmini — rotation re-keys
# only future pseudonyms, existing rows keep the old hash/name.
FEEDBACK_PSEUDONYM_SECRET: ${FEEDBACK_PSEUDONYM_SECRET:?missing in .env.macmini}
CORS_ORIGINS: https://mana.how
CORS_ORIGINS: https://mana.how,https://community.mana.how
ports:
- "3064:3064"
healthcheck:
@ -950,7 +950,7 @@ services:
# /api/v1/(public/)feedback/* endpoints directly; SSR uses the
# internal docker-network URL.
PUBLIC_MANA_ANALYTICS_URL: http://mana-analytics:3064
PUBLIC_MANA_ANALYTICS_URL_CLIENT: https://analytics.mana.how
PUBLIC_MANA_ANALYTICS_URL_CLIENT: https://community.mana.how
# mana-ai background Mission Runner. Browser calls the audit
# endpoint (/api/v1/me/ai-audit) to render the Workbench
# "Datenzugriff" tab. SSR doesn't hit this service directly.