-
Notifications
You must be signed in to change notification settings - Fork 226
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1653 from appwrite/fix-sentry-integrations
Fix: Sentry integrations, DSN format
- Loading branch information
Showing
2 changed files
with
4 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -43,13 +43,13 @@ Head to **Settings** > **Projects** > Select your Sentry project > **Client Keys | |
|
||
For this step, you must [self-host Appwrite](https://appwrite.io/docs/advanced/self-hosting) if you haven’t already. | ||
|
||
To add the Sentry provider, you need to slightly reconfigure your DSN. Your Sentry DSN is made up of 3 parts: **public key**, **URI**, and **project ID**. The Appwrite logging configuration expects a string in the format `SENTRY_PUBLIC_KEY;SENTRY_PROJECT_ID`. For example, if your Sentry DSN is `https://[email protected]/1`, then the Appwrite logging configuration will be `public;1`. | ||
To add the Sentry provider, you need to slightly reconfigure your DSN. Your Sentry DSN is made up of 3 parts: **project ID**, **public key**, and **host**. The Appwrite logging configuration expects a string in the format `SENTRY_PROJECT_ID;SENTRY_PUBLIC_KEY@SENTRY_HOST`. For example, if your Sentry DSN is `https://[email protected]/1`, then the Appwrite logging configuration will be `1;[email protected]`. | ||
|
||
Visit the `.env` file created for your Appwrite instance and update the following environment variables: | ||
|
||
```bash | ||
_APP_LOGGING_PROVIDER=sentry | ||
_APP_LOGGING_CONFIG=SENTRY_PUBLIC_KEY;SENTRY_PROJECT_ID | ||
_APP_LOGGING_CONFIG=SENTRY_PROJECT_ID;SENTRY_PUBLIC_KEY@SENTRY_HOST | ||
``` | ||
|
||
After that, run the following Docker Compose commands in your terminal to restart your Appwrite containers and verify if the changes have been successfully applied: | ||
|
@@ -64,7 +64,7 @@ docker compose exec appwrite vars | |
Once the Sentry provider is configured, run the following command in your terminal: | ||
|
||
```bash | ||
docker compose exec appwrite ssl --domain="wrongdomain.com" | ||
docker compose exec appwrite ssl --domain="your-domain.com" | ||
``` | ||
|
||
Doing so will show errors in your Sentry **Issues** page. | ||
|