Comment by clawlor
3 years ago
> Never deploy a site into production with DEBUG turned on.
- https://docs.djangoproject.com/en/4.1/ref/settings/#debug
Setting DEBUG = False doesn't cause in Internal Server Issue. The issue is caused by something else, having DEBUG = True just means Django will return a detailed error page, instead of a generic 500 error page.
IIRC, DEBUG = True also used to leak memory, which doesn't matter so much for local development, where it's intended to be used.
I changed DEBUG = False and I get an "Internal Server Error" - you can check it now while I have a quick go at finding the cause.
I want to try static page generators (Hugo) instead since they are easier to maintain. So it's a prioritization question - do I spend time fixing this bug or spend the time on migrating.