Skip to content

Commit 4d02c7e

Browse files
committed
Fix docs
1 parent f59b0c1 commit 4d02c7e

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

docs/monitoring.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,9 @@ for your project under `Organization > Projects > Project > Name`
5151
In the 'build' section of the [Dockerfile](../other/Dockerfile), there is an
5252
example of how to pass `SENTRY_AUTH_TOKEN` secret, so it is available to Vite
5353
when `npm run build` is run. You may also uncomment and hard code your
54-
`SENTRY_ORG` and `SENTRY_PROJECT` values. Setup up your secrets in
54+
`SENTRY_ORG` and `SENTRY_PROJECT` values, both in
55+
[Dockerfile](../other/Dockerfile) and in the "Create Sentry release" step of the
56+
[`deploy`](../.github/workflows/deploy.yml) script. Setup up your secrets in
5557
[GitHub Actions secrets](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions).
5658
You can do the same for any other secret (environment variable) you need at
5759
build time, just make sure those secrets (variables) are available on the CI

0 commit comments

Comments
 (0)