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

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

config: initialize routes directly from RootController...
config: initialize routes directly from RootController Let RootController directly initialize routes instead of app_cfg injecting the mapper. For test initialization, we also need a handle to the mapper. We could either recreate it (but fragile if the real mapper initialization is changed later) or obtain it from a fresh RootController. This commit opts for the latter.
timeless@gmail.com - - Load All Authors

File last commit:

r5817:87ac42db default
r6530:69cd0c05 default
Show More
debugging.rst
33 lines | 1.2 KiB | text/x-rst | RstLexer
/ docs / usage / debugging.rst
History | Annotation | Raw |Copy content |Copy permalink

Debugging Kallithea

If you encounter problems with Kallithea, here are some instructions on how to debug them.

Note

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

Enable detailed debug

Kallithea uses the standard Python logging module to log its output. By default only loggers with INFO level are displayed. To enable full output change level = DEBUG for all logging handlers in the currently used .ini file. This change will allow you to see much more detailed output in the log file 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 the .ini file. This will trigger an interactive debugger each time there is an error in the browser, or send a http link if an error occurred in the backend. This is a great tool for fast debugging as you get a handy Python console right in the web view.

Warning

NEVER ENABLE THIS ON PRODUCTION! The interactive console can be a serious security threat to your system.