Rely on SENTRY_ENVIRONMENT instead of using just ENVIRONMENT

pull/1/head
Luca 3 years ago
parent 9032968bc0
commit 5b0ca61d17

@ -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,
) )

Loading…
Cancel
Save