Technically speaking, setting DEBUG=False on a production system does not render it un-debuggable. You can still debug and work with such deployments but expect resistance. An ancient approach to debugging ANY production environment is to liberally sprinkle printf (or the django log equivalent) everywhere in your code base. This has its drawbacks, but you could always push out a temporary patch to production to investigate something and revert afterwards.
Note: I do not recommend this approach. Always try to replicate issues in a development environment. Production meddling should only be a last resort and is usually an indication of a problem external to django anyways. -Abraham V. On Monday, 4 January 2016 23:03:26 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 django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. 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/532d2ae4-6e38-46a7-9d5e-f17f0f77161a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
