##// END OF EJS Templates
upstream » kallithea
RSS

Clone from https://kallithea-scm.org/repos/kallithea

docs: rework stuff...
docs: rework stuff The existing docs were far from how we wanted it to be. There was so much to do and it is not feasible to do that cleanup it in clean patches. Instead, I took a sweep through the docs and changed what I thought could benefit from a change: structure, examples, advices, language, markup, content, etc.
Mads Kiilerich - - Load All Authors

File last commit:

r4902:03bbd33b default
r4902:03bbd33b default
Show More
debugging.rst
30 lines | 1.1 KiB | text/x-rst | RstLexer
/ docs / usage / debugging.rst
History | Annotation | Raw |Copy content |Copy permalink

Debugging Kallithea

If you encountered problems with Kallithea here are some instructions how to possibly debug them.

** First make sure you're using the latest version available.**

Enable detailed debug

Kallithea uses standard python logging modules to log it's output. By default only loggers with INFO level are displayed. To enable full output change level = DEBUG for all logging handlers in currently used .ini file. This change will allow to see much more detailed output in the logfile or console. This generally helps a lot to track issues.

Enable interactive debug mode

To enable interactive debug mode simply comment out set debug = false in .ini file, this will trigger and interactive debugger each time there an error in browser, or send a http link if error occured in the backend. This is a great tool for fast debugging as you get a handy python console right in the web view. ** NEVER ENABLE THIS ON PRODUCTION ** the interactive console can be a serious security threat to you system.