##// END OF EJS Templates
docs: reorganize index page...
docs: reorganize index page Reorganize the index page of the manual into three main sections: administrator guide, user guide, developer guide. In principle, administrators, users and developers are independent roles that can be fulfilled by different people. 'Administrators' install, configure and maintain Kallithea. They have 'admin' privilege in the web interface. 'Users' do not have access to the Kallithea installation files. They can only access the web interface, and generally do not have 'admin' privilege. They may be the owner of repositories, repository groups, or user groups, and as such modify the settings of these objects, even though they cannot modify the settings of Kallithea itself. 'Developers' modify the Kallithea source code. They may or may not contribute these changes back to the Kallithea community. The 'Readme' section is a bit outside of this classification. As it serves as a basic introduction to Kallithea, it is kept first. The 'Index' and 'Search' functionality are not really 'part of' the manual, so should not be under 'Other topics'. Instead they are put at the very top so they are readily visible. This commit is only changing the index page. Subsequent commits can move and split some documentation files in the repository to mirror this structure. For example, the 'Version control systems support' page has information for administrators (ini settings and importing existing repositories) as well as for users (handling Mercurial subrepositories).

File last commit:

r6298:9c6f7178 merge default
r7254:e71216a1 default
Show More
troubleshooting.rst
75 lines | 2.3 KiB | text/x-rst | RstLexer
/ docs / usage / troubleshooting.rst

Troubleshooting


Q:Can't install celery/rabbitmq?
A:Don't worry. Kallithea works without them, too. No extra setup is required. Try out the great Celery docs for further help.

Q:Long lasting push timeouts?
A:Make sure you set a longer timeout in your proxy/fcgi settings. Timeouts are caused by the http server and not Kallithea.

Q:Large pushes timeouts?
A:Make sure you set a proper max_body_size for the http server. Very often Apache, Nginx, or other http servers kill the connection due to to large body.

Q:Apache doesn't pass basicAuth on pull/push?
A:Make sure you added WSGIPassAuthorization true.

Q:Git fails on push/pull?
A:Make sure you're using a WSGI http server that can handle chunked encoding such as waitress or gunicorn.

Q:How can I use hooks in Kallithea?
A:It's easy if they are Python hooks: just use advanced link in hooks section in Admin panel, that works only for Mercurial. If you want to use Git hooks, just install th proper one in the repository, e.g., create a file /gitrepo/hooks/pre-receive. 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
A:Please read: https://docs.djangoproject.com/en/dev/howto/deployment/wsgi/modwsgi/#if-you-get-a-unicodeencodeerror.

Q:Requests hanging on Windows
A:Please try out with disabled Antivirus software, there are some known problems with Eset Antivirus. Make sure you have installed the latest Windows patches (especially KB2789397).