fix(analytics): expose UMAMI_WEBSITE_ID to client to enable tracking proxy
All checks were successful
Build & Deploy / 🔍 Prepare (push) Successful in 12s
Build & Deploy / 🧪 QA (push) Successful in 2m0s
Build & Deploy / 🏗️ Build (push) Successful in 11m25s
Build & Deploy / 🚀 Deploy (push) Successful in 28s
Build & Deploy / 🧪 Smoke Test (push) Successful in 2m27s
Build & Deploy / ⚡ Lighthouse (push) Successful in 5m39s
Build & Deploy / 🔔 Notify (push) Successful in 1s

This commit is contained in:
2026-02-20 12:11:45 +01:00
parent 16d06d3275
commit e20d7f42c0
3 changed files with 6 additions and 6 deletions

View File

@@ -35,9 +35,9 @@ function createConfig() {
analytics: {
umami: {
websiteId: env.UMAMI_WEBSITE_ID,
websiteId: env.NEXT_PUBLIC_UMAMI_WEBSITE_ID,
apiEndpoint: env.UMAMI_API_ENDPOINT || 'https://analytics.infra.mintel.me',
enabled: Boolean(env.UMAMI_WEBSITE_ID),
enabled: Boolean(env.NEXT_PUBLIC_UMAMI_WEBSITE_ID),
},
},

View File

@@ -31,7 +31,7 @@ const envExtension = {
INFRA_DIRECTUS_TOKEN: z.string().optional(),
// Analytics
UMAMI_WEBSITE_ID: z.string().optional(),
NEXT_PUBLIC_UMAMI_WEBSITE_ID: z.string().optional(),
UMAMI_API_ENDPOINT: z.string().optional(),
// Mail Configuration