Mercurial > kallithea
view docs/usage/debugging.rst @ 4245:3315e9263a53
Use Conservancy's Kallithea Committee address as author_email.
the setup.py needs an author_email setting. Since this is a fork, the
author_email should be the individuals responsible for the fork. This
address reaches the Kallithea Committee at Conservancy.
| author | Bradley M. Kuhn <bkuhn@sfconservancy.org> |
|---|---|
| date | Fri, 04 Jul 2014 09:40:56 -0400 |
| parents | e73a69cb98dc |
| children | 03bbd33bc084 |
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.