Skip to content

Commit 60d3071

Browse files
Copilotrenemadsen
andcommitted
Add Sentry configuration documentation to README
Co-authored-by: renemadsen <[email protected]>
1 parent 171fe8a commit 60d3071

File tree

1 file changed

+23
-0
lines changed

1 file changed

+23
-0
lines changed

README.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,29 @@ You need to create an account for Microting API and get your access credentials.
4444

4545
* Call Microting at +45 66 11 10 66 to get started.
4646

47+
## Sentry Configuration
48+
49+
Sentry error tracking is enabled by default in production environments but disabled in development mode to prevent unnecessary test data collection.
50+
51+
### Development Mode
52+
When running locally with `yarn start`, Sentry is automatically disabled via the `environment.ts` configuration file where `enableSentry: false`.
53+
54+
### Production Mode
55+
In production builds, Sentry is enabled through `environment.prod.ts` where `enableSentry: true`.
56+
57+
### Docker Configuration
58+
When building Docker images, you can control Sentry behavior using the `DISABLE_SENTRY` build argument:
59+
60+
```bash
61+
# Disable Sentry for testing/CI environments
62+
docker build --build-arg DISABLE_SENTRY=true -t my-image .
63+
64+
# Enable Sentry for production (default behavior)
65+
docker build -t my-image .
66+
```
67+
68+
The `DISABLE_SENTRY` environment variable can be set to `true` or `1` to disable Sentry in both the Angular frontend and C# backend.
69+
4770
## Testing
4871

4972
### E2E Test Migration

0 commit comments

Comments
 (0)