Mercurial > kallithea
diff docs/setup.rst @ 912:8378122aa408 beta
docs: changelog + setup update
author | Marcin Kuzminski <marcin@python-works.com> |
---|---|
date | Tue, 04 Jan 2011 00:25:42 +0100 |
parents | 1fed3c9161bb |
children | c44b3c9b9f7f |
line wrap: on
line diff
--- a/docs/setup.rst Mon Jan 03 10:39:36 2011 +0100 +++ b/docs/setup.rst Tue Jan 04 00:25:42 2011 +0100 @@ -50,6 +50,31 @@ anonymous, permissions settings. As well as edit more advanced options on users and repositories +Using RhodeCode with SSH +------------------------ + +RhodeCode repository structures are kept in directories with the same name +as the project, when using repository groups, each group is a a subdirectory. +This will allow You to use ssh for accessing repositories quite easy. There +are some exceptions when using ssh for accessing repositories. + +You have to make sure that the webserver as well as the ssh users have unix +permission for directories. Secondly when using ssh rhodecode will not +authenticate those requests and permissions set by the web interface will not +work on the repositories accessed via ssh. There is a solution to this to use +auth hooks, that connects to rhodecode db, and runs check functions for +permissions. + +TODO: post more info on this ! + +if Your main directory (the same as set in RhodeCode settings) is set to +for example `\home\hg` and repository You are using is `rhodecode` + +The command runned should look like this:: + hg clone ssh://user@server.com/home/hg/rhodecode + +Using external tools such as mercurial server or using ssh key based auth is +fully supported. Setting up Whoosh full text search ----------------------------------