What I do is to log things in log files. All exceptions are logged in
error.log files and I've enabled admin mail which sends me an email
whenever there is an exception.
So basically logs and emails are quite helpful in debugging and makes it
smooth.
On Wed, 6 Jan 2016 at 10:20 Web Architect wrot
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 wit
If it is the exception tracebacks you are after, consider setting up a
Sentry ( https://getsentry.com/ ) server to send the error / exception logs
of all your sites to. Whenever something bad happens, it'll show up there,
with full tracebacks.
Greetings,
Remco Gerlich
On Mon, Jan 4, 2016 at 6:33
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)
You don't say what your front end is. There are ways to use pdb with
apache, look for advise on the modwsgi site.
But if you are in production, rather than just bringing up the instance
that will be production, you may not want to interrupt.
Be sure that you can't reproduce the problem in the de
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.
6 matches
Mail list logo
