Mercurial > kallithea
view docs/usage/debugging.rst @ 4936:bcc637ea79a8
template: link the last revision in the file browser to the changeset
author | Andrew Shadura <andrew@shadura.me> |
---|---|
date | Sat, 21 Mar 2015 22:23:44 +0100 |
parents | 03bbd33bc084 |
children | 4e6dfdb3fa01 |
line wrap: on
line source
.. _debugging: =================== 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.