kallithea Files · docs/usage/debugging.rst

Files @ f92d08061a24

Branch filter:

Location: kallithea/docs/usage/debugging.rst

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

domruf

summary: use shared changelog_table implementation on summary page

The main purpose of this change is to simplify code and avoid duplication.

Using the shared implementation also happens to give a slightly different view
of the changesets. There will be no table headers, the columns are shown in
different order, author gravatars are shown, commit messages can be expanded,
and there is slightly different styling.

Small remaining amounts of template code is moved from
changelog_summary_data.html to summary.html.

Patch modified by Mads Kiilerich.

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