refactor: improve security by moving Sentry secrets to environment variables

To enhance security, Sentry authentication tokens and project IDs are now passed as environment variables instead of being exposed in the workflow configuration. This change reduces the risk of sensitive information leakage during the build process. Additionally, the example environment file has been updated to comment out the Sentry-related variables, further protecting against accidental exposure.
This commit is contained in:
ccbikai
2024-10-15 21:11:47 +08:00
parent a44eeb76eb
commit bf2ecfe7a0
3 changed files with 5 additions and 6 deletions

View File

@@ -17,9 +17,9 @@ HEADER_INJECT=HEADER_INJECT
NO_FOLLOW=false
NO_INDEX=false
SENTRY_AUTH_TOKEN=
#SENTRY_AUTH_TOKEN=
SENTRY_DSN=
SENTRY_PROJECT=
#SENTRY_PROJECT=
TELEGRAM_HOST=telegram.dog
STATIC_PROXY=""