Thanks all for the responses and I would certainly consider them for production level debugging. I understand that application level debugging could be achieved by various logging mechanisms or tools.
But one of my main concern is the platform level debugging where in if anything goes wrong with any package. For example, recently when I had set DEBUG=False, the backend was throwing HTTP 500. I was completely clueless what was happening. After deep debugging in the code, I figured out that 'compress js' that was being used in templates - it seemed was not being supported when DEBUG=False. It took some time to figure this out. Had there been a log or some mechanism, debugging would have been lot easier and quicker. On Monday, January 4, 2016 at 11:03:26 PM UTC+5:30, Web Architect wrote: > > Hi, > > Is there a way to debug Django when DEBUG is set to False in settings.py > (for example on production)? > > The reason for asking the above is if we face any issue with DEBUG set to > False and if we need to debug. > > We are new to Django and we are building an ecommerce platform based on > Django. > > Would appreciate if anyone could help with the above? > > Thanks. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/1550f31d-bcf7-430a-849f-f219e5ba3077%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
