Mercurial > kallithea
view docs/usage/locking.rst @ 4815:64b1a2320bcb
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
author | Denis Blanchette <dblanchette@coveo.com> |
---|---|
date | Mon, 02 Feb 2015 17:20:08 -0500 |
parents | e73a69cb98dc |
children | 03bbd33bc084 |
line wrap: on
line source
.. _locking: =================================== Kallithea repository locking system =================================== | Repos with **locking function=disabled** is the default, that's how repos work today. | Repos with **locking function=enabled** behaves like follows: Repos have a state called `locked` that can be true or false. The hg/git commands `hg/git clone`, `hg/git pull`, and `hg/git push` influence this state: - The command `hg/git pull <repo>` will lock that repo (locked=true) if the user has write/admin permissions on this repo - The command `hg/git clone <repo>` will lock that repo (locked=true) if the user has write/admin permissions on this repo Kallithea will remember the user id who locked the repo only this specific user can unlock the repo (locked=false) by calling - `hg/git push <repo>` every other command on that repo from this user and every command from any other user will result in http return code 423 (locked) additionally the http error includes the <user> that locked the repo (e.g. “repository <repo> locked by user <user>”) So the scenario of use for repos with `locking function` enabled is that every initial clone and every pull gives users (with write permission) the exclusive right to do a push. Each repo can be manually unlocked by admin from the repo settings menu.