docs: update Windows installation documentation for Windows 7/Server 2008 R2 and newer Update to the Windows installation documentation following my setup experience on our production server. Changes : * Use of Microsoft Visual C++ Compiler for Python 2.7 which simplifies matter versus installing Visual Studio 2008 Express, because it removes the need to use the Visual Studio 2008 command prompt. It is also a lot smaller to download and install. Unfortunately, this means the instruction will only work on the same platforms as those which are supported by the compiler. * For that reason, I split the documentation into newer and older Windows. * Added more explanations where I feel it was necessary based on my experience * Added explanation on Git (Warning : I did not try this part) * Instructions assumes x64 instead of Win32. * Clarified titles * Grammar Potential issues: * I have the user install pip system wide so that virtualenv installation is easier (especially if using Python 2.7.9 which already includes pip). One may prefer to install virtualenv and the pip in the virtual environment (I know of no good reason, but it could happen). * Removed some line feeds that I found useless. I do not know the .rst format, they might be needed. It makes no difference when the documentation is generated using make.bat, so I am not sure Potential improvements: * Instructions on using srvany.exe to install as a Windows service * Instructions to make a reverse proxy using Apache * Instructions to make a reverse proxy using IIS

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