kallithea Files · docs/usage/debugging.rst

Files @ 3fb0ce6de10d

Branch filter:

Location: kallithea/docs/usage/debugging.rst

3fb0ce6de10d 1.2 KiB text/prs.fallenstein.rst Show Annotation Show as Raw Download as Raw

Mads Kiilerich

celery: replace loader.PylonsSettingsProxy with a simple configuration object

The proxy was quite complex and did all the conversion at runtime, making it
hard to figure out exactly what it was doing.

Instead, just create a simple configuration object as described on
http://docs.celeryproject.org/en/3.1/userguide/application.html and convert all
relevant config settings up front. We don't convert all config settings, but
only the ones Celery seems to be interested in. The value conversion heuristics
are the same as before and still seem quite fragile.

.. _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 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.