kallithea Files · docs/usage/debugging.rst

Files @ 238486bb71ab

Branch filter:

Location: kallithea/docs/usage/debugging.rst

238486bb71ab 1.1 KiB text/prs.fallenstein.rst Show Annotation Show as Raw Download as Raw

Marcin Kuzminski

Switched handling of RhodeCode extra params in consistent way
- use only os.environ for both hg and git
- hacking ui objects was bad
- os.environ allows easier to call rhodecode hooks externally

.. _debugging:

===================
Debugging RhodeCode
===================

If you encountered problems with RhodeCode here are some instructions how to
possibly debug them.

** First make sure you're using the latest version available.**

enable detailed debug
---------------------

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