Re: Change settings.DEBUG in response to a request's source

Although I can't comment on your individual use case, it's better to enable remote error collection using something like Sentry or BugSnag. Both also support integration with other languages, such as JS, which is very handy when tracking down front end problems. There are lesser alternatives such

Change settings.DEBUG in response to a request's source

I'm writing an app where it'd be super helpful for logged-in users from my company to see error pages and the like as though the app was running with DEBUG=True, while still preventing ordinary users from seeing that output. I see that the docs strongly warn me against changing settings at