-
Notifications
You must be signed in to change notification settings - Fork 53
Description
Thank you for this, I've been using this for a while now without running into any issues.
So from sentry sourcemaps docs
If you want to keep your source maps secret and choose not to upload your source maps directly to Sentry, you can enable the “Security Token” option in your project settings. This will cause outbound requests from Sentry’s servers to URLs originating from your “Allowed Domains” to have the HTTP header “X-Sentry-Token: {token}” appended, where {token} is a secure value you define. You can then configure your web server to allow access to your source maps when this header/token pair is present. You can alternatively override the default header name (X-Sentry-Token) and use HTTP Basic Authentication, e.g. by passing “Authorization: Basic {encoded_password}”.
This is useful when you want to generate this secret token during build time and add it to both webserver config (e.g. nginx) to allow and also making sure that sentry is configured to use the same key. The UI can be found under Project Settings.
Is something like this possible via env variables?