We use sentry_client to capture errors in our TYPO3 installations on testing, staging and production environments.
On local development environments we disable sentry_client, because those errors are handled by the developer instantly.
We disable sentry_client by adding some code to AdditionalConfiguration.php:
This works but has one problem: When someone installs an extension or modifies extension configuration in the TYPO3 backend, the empty DSN is written into LocalConfiguration.php. When committing changes, people need to take care to not commit that line.
Is there a better way to disable sentry_client locally?
christophlehmann
commented
1 year ago
We use sentry_client to capture errors in our TYPO3 installations on testing, staging and production environments. On local development environments we disable sentry_client, because those errors are handled by the developer instantly.
We disable sentry_client by adding some code to
AdditionalConfiguration.php:This works but has one problem: When someone installs an extension or modifies extension configuration in the TYPO3 backend, the empty DSN is written into
LocalConfiguration.php. When committing changes, people need to take care to not commit that line.Is there a better way to disable sentry_client locally?