Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Settings improvements #107

Merged
merged 5 commits into from
Aug 1, 2024
Merged

Settings improvements #107

merged 5 commits into from
Aug 1, 2024

Conversation

friedelwolff
Copy link
Contributor

No description provided.

... by removing it.

The setting for SHOW_TOOLBAR_CALLBACK seems to have been an attempt
to work around issues when running inside docker. Debug toolbar tries
to handle this case, but it doesn't work sufficiently (at least in my
case). The documentation has an opinion on this matter:

  Do not use
    DEBUG_TOOLBAR_CONFIG = {"SHOW_TOOLBAR_CALLBACK": lambda request: DEBUG}
  in your project’s settings.py file.

This commit is longer than I'd like, but the setting of INTERNAL_IPS
seems to really fix it, and solves the fact that the debug context
processor wasn't working either. With this fixed, {% debug %} works
in templates.

INTERNAL_IPS should best contain IP addresses rather than hostnames.

IS_RUNNING_TESTS... no idea why we would want the toolbar while
running tests.
@friedelwolff friedelwolff merged commit 3a16eab into develop Aug 1, 2024
2 checks passed
@friedelwolff friedelwolff deleted the settings-improvement branch August 1, 2024 17:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant