Monitoring settings (Sentry, Umami) and the CSP origins come from the build environment
One build per environment: PROD_* variables for the production artifact, TEST_* for the test build and the CSP check. The build fails when a variable is empty. Tests use the production values from config/monitoringTestEnv.ts. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,12 @@
|
||||
// De monitoringinstellingen die de tests als productiebuild zien. De echte
|
||||
// waarden komen in de pipeline uit de Gitea-variabelen PROD_SENTRY_DSN,
|
||||
// PROD_UMAMI_SCRIPT_URL en PROD_UMAMI_WEBSITE_ID (en TEST_...); deze openbare
|
||||
// waarden zijn er hetzelfde als, zodat de gegenereerde serverconfiguratie en de
|
||||
// CSP in de tests vergelijkbaar blijven. Zie src/monitoring/config.ts.
|
||||
export const monitoringTestEnv = {
|
||||
VITE_APP_ENV: 'production',
|
||||
VITE_SENTRY_DSN:
|
||||
'https://12ec77dcc3216a98b96d3fb3dac13f66@o4511795618185216.ingest.de.sentry.io/4512282287472720',
|
||||
VITE_UMAMI_SCRIPT_URL: 'https://analytics.slpsoftware.nl/script.js',
|
||||
VITE_UMAMI_WEBSITE_ID: '3edbb7d1-4388-4f2d-9cef-11ade88ace96',
|
||||
};
|
||||
Reference in New Issue
Block a user