kontakt
/
shiftregister
2
0
Fork 0
Code

Rely on SENTRY_ENVIRONMENT instead of using just ENVIRONMENT

This commit is contained in:
Luca 2022-04-27 14:12:03 +02:00
parent 9032968bc0
commit 5b0ca61d17
1 changed files with 1 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
shiftregister/settings.py
View File

@ -28,10 +28,8 @@ SECRET_KEY = getenv(
"SECRET_KEY", "django-insecure-pdgzgd_!w&&cfqc%r&!v_^6pgf!sza=2wim67()!(kaf7_6-5)" "SECRET_KEY", "django-insecure-pdgzgd_!w&&cfqc%r&!v_^6pgf!sza=2wim67()!(kaf7_6-5)"
) )
ENVIRONMENT = getenv("ENVIRONMENT", "development")
# SECURITY WARNING: don't run with debug turned on in production! # SECURITY WARNING: don't run with debug turned on in production!
DEBUG = ENVIRONMENT == "development" DEBUG = getenv("ENVIRONMENT", "development") == "development"
ALLOWED_HOSTS = list(filter(lambda s: s != "", getenv("ALLOWED_HOSTS", "").split(","))) ALLOWED_HOSTS = list(filter(lambda s: s != "", getenv("ALLOWED_HOSTS", "").split(",")))
@ -163,5 +161,4 @@ if getenv("SENTRY_DSN"):
integrations=[CeleryIntegration(), DjangoIntegration()], integrations=[CeleryIntegration(), DjangoIntegration()],
auto_session_tracking=False, auto_session_tracking=False,
traces_sample_rate=0, traces_sample_rate=0,
environment=ENVIRONMENT,
) )