jlengrand/bugsink
1
0
Fork 0
mirror of https://github.com/jlengrand/bugsink.git synced 2026-03-10 08:01:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

Hide development server warning: development only

Browse Source
This commit is contained in:
Klaas van Schelven
2025-09-27 13:35:31 +02:00
parent d0e7b75dbb
commit a20e10ef09
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
bugsink/settings/default.py
View File

@@ -6,10 +6,6 @@ from pathlib import Path
from django.utils.log import DEFAULT_LOGGING
# Hide development server warning
# https://docs.djangoproject.com/en/stable/ref/django-admin/#envvar-DJANGO_RUNSERVER_HIDE_WARNING
os.environ["DJANGO_RUNSERVER_HIDE_WARNING"] = "true"
# We have a single file for our default settings, and expect (if they use the singleserver setup) the end-users to
# configure their setup using a single bugsink_conf.py also. To be able to have (slightly) different settings for e.g.
# logging for various commands, we expose a variable I_AM_RUNNING that can be used to determine what command is being

4
bugsink/settings/development.py
View File

@@ -8,6 +8,10 @@ from sentry_sdk_extensions.transport import MoreLoudlyFailingTransport
from bugsink.conf_utils import deduce_allowed_hosts, eat_your_own_dogfood, deduce_script_name
# Hide development server warning
# https://docs.djangoproject.com/en/stable/ref/django-admin/#envvar-DJANGO_RUNSERVER_HIDE_WARNING
os.environ["DJANGO_RUNSERVER_HIDE_WARNING"] = "true"
# no_bandit_expl: _development_ settings, we know that this is insecure; would fail to deploy in prod if (as configured)
# the django checks (with --check --deploy) are run.