fix(analytics): update Umami website ID after database reset

The Umami database was re-initialized with empty website table. Created
new ManaCore Web website in Umami and updated the ID in docker-compose
and .env.development. Fixes stats.mana.how 400 errors.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Till JS 2026-04-03 16:23:09 +02:00
parent 6a75f3fca1
commit f592464f61
2 changed files with 2 additions and 2 deletions

View file

@ -120,7 +120,7 @@ STRIPE_PORTAL_CONFIG_ID=bpc_1T1PFdAZjQCYS0ZJEhF9ob7q
# All app modules are tracked under the unified ManaCore website ID.
# Module segmentation happens via the `module` event property (see analytics.ts).
# Register new sites at https://stats.mana.how
UMAMI_WEBSITE_ID_MANACORE=face76f4-2d3e-42be-b8c8-0ea03f33a462
UMAMI_WEBSITE_ID_MANACORE=32777167-e026-4618-933a-3429120b479b
# Landing Page Website IDs (separate Astro sites, each needs its own ID)
UMAMI_WEBSITE_ID_CHAT_LANDING=a264b165-80d2-47ab-91f4-2efc01de0b66