Re: ./manage.py settings

Django already attempt to mask security-sensitive settings in the debug page. It would make sense to do the same by default for the output of diffsetting: obfuscate secrets. A --include-secrets flag (on any other name) would show the secrets. -- Aymeric. > On 12 Jun 2020, at 13:59, Jure Er

Re: ./manage.py settings

There was a GSoC proposal this year for a SecretsManager that could conceivably make what you suggest possible. Wasn't accepted though. Not sure if it'

Re: ./manage.py settings

Hi, Just a thought that came to my mind: It would be useful to have a command that dumps the run-time settings, but automatically replaces secrets with dummy values. I think this should not be too hard to do for Django's own secret settings, and maybe it can also be done for some known common thi

Re: ./manage.py settings

It wasn't discussed indeed, nice command, thank you ! -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+un

Re: ./manage.py settings

I've always used `diffsettings` to print my settings for debugging purposes, and `diffsettings` combined with `| grep` to filter down to specific settings options. Was this option discussed in the IRC thread? https://docs.djangoproject.com/en/2.2/ref/django-admin/#diffsettings Best, Ion On Thu,

./manage.py settings

Hi all, So, just on #django IRC channel there was a user trying to help another one, asking for some settings through ./manage.py shell etc ... A discussion that went kind of like "Print out your settings" "How would I print, I tried that, I'm in settings.py" "With ... print()" "but in the shel