---------------

Custom Mercurial hooks can be managed in a similar way to that used in ``.hgrc`` files.

To manage hooks, choose *Admin > Settings > Hooks*.

To add another custom hook simply fill in the first textbox with

``<name>.<hook_type>`` and the second with the hook path. Example hooks

can be found in ``kallithea.lib.hooks``.

Kallithea will also use some hooks internally. They cannot be modified, but

some of them can be enabled or disabled in the *VCS* section.

Changing default encoding

-------------------------

By default, Kallithea uses UTF-8 encoding.

This is configurable as ``default_encoding`` in the .ini file.

This affects many parts in Kallithea including user names, filenames, and

encoding of commit messages. In addition Kallithea can detect if the ``chardet``

library is installed. If ``chardet`` is detected Kallithea will fallback to it

when there are encode/decode errors.

10. Reinstall internal Git repository hooks

-------------------------------------------

It is possible that an upgrade involves changes to the Git hooks installed by

Kallithea. As these hooks are created inside the repositories on the server

filesystem, they are not updated automatically when upgrading Kallithea itself.

To update the hooks of your Git repositories, run::

    kallithea-cli repo-scan -c my.ini --install-git-hooks

Or:

* Go to *Admin > Settings > Remap and Rescan*

* Select the checkbox *Install Git hooks*

* Click the button *Rescan repositories*

.. note::

    Kallithea does not use hooks on Mercurial repositories. This step is thus

    not necessary if you only have Mercurial repositories.

|

:Q: **How can I use hooks in Kallithea?**

:A: If using Mercurial, use *Admin > Settings > Hooks* to install

    global hooks. Inside the hooks, you can use the current working directory to

    control different behaviour for different repositories.

    If using Git, install the hooks manually in each repository, for example by

    creating a file ``gitrepo/hooks/pre-receive``.

    Note that Kallithea uses the ``post-receive`` hook internally.

    Kallithea will not work properly if another post-receive hook is installed instead.

    You might also accidentally overwrite your own post-receive hook with the Kallithea hook.

    You can also use Kallithea-extensions to connect to callback hooks,

    for both Git and Mercurial.

|

:Q: **Kallithea is slow for me, how can I make it faster?**

:A: See the :ref:`performance` section.

|

:Q: **UnicodeDecodeError on Apache mod_wsgi**

"""Kallithea Git hook

This hook is installed and maintained by Kallithea. It will be overwritten

by Kallithea - don't customize it manually!

When Kallithea invokes Git, the KALLITHEA_EXTRAS environment variable will

contain additional info like the Kallithea instance and user info that this

hook will use.

"""

import os

import sys

import kallithea.bin.vcs_hooks

# Set output mode on windows to binary for stderr.

# This prevents python (or the windows console) from replacing \n with \r\n.

# Git doesn't display remote output lines that contain \r,

# and therefore without this modification git would display empty lines

# instead of the exception output.

if sys.platform == "win32":

    import msvcrt

    msvcrt.setmode(sys.stderr.fileno(), os.O_BINARY)

KALLITHEA_HOOK_VER = '_TMPL_'

os.environ['KALLITHEA_HOOK_VER'] = KALLITHEA_HOOK_VER

def main():

    repo_path = os.path.abspath('.')

    git_stdin_lines = sys.stdin.readlines()

if __name__ == '__main__':

    main()