Mercurial > kallithea
view docs/usage/debugging.rst @ 5275:8e72e78a7d9e
archive: refactor archive handling
Use file descriptors in a more sane way.
author | Mads Kiilerich <madski@unity3d.com> |
---|---|
date | Mon, 20 Jul 2015 15:11:42 +0200 |
parents | 4e6dfdb3fa01 |
children | fbbe80e3322b |
line wrap: on
line source
.. _debugging: =================== 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 occured 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.