From a20e10ef09143569eb6d0d6846ac813abec46041 Mon Sep 17 00:00:00 2001 From: Klaas van Schelven Date: Sat, 27 Sep 2025 13:35:31 +0200 Subject: [PATCH] Hide development server warning: development only --- bugsink/settings/default.py | 4 ---- bugsink/settings/development.py | 4 ++++ 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/bugsink/settings/default.py b/bugsink/settings/default.py index 0bcf3c4..cc2b469 100644 --- a/bugsink/settings/default.py +++ b/bugsink/settings/default.py @@ -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 diff --git a/bugsink/settings/development.py b/bugsink/settings/development.py index eb95575..4e1a0ca 100644 --- a/bugsink/settings/development.py +++ b/bugsink/settings/development.py @@ -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.