Files
@ 6df08d78f8e7
Branch filter:
Location: kallithea/docs/usage/locking.rst - annotation
6df08d78f8e7
1.1 KiB
text/prs.fallenstein.rst
cli: fill in git_hook_interpreter at 'config-create' time to really fix potentially invalid interpreter in git hooks (Issue #333)
When generating a configuration file using 'kallithea-cli config-create', it is
probably using the right Python interpreter, so fill in the current Python
executable as 'git_hook_interpreter' in the generated file.
There should thus rarely be any need to configure this manually, and issue #333
will *really* be fixed.
As this causes an absolute path to be encoded inside the ini file, moving
the virtualenv will require updating this path.
For development.ini we do not want to hardcode any path and are happy to leave
it using the old heuristics at runtime.
Suggested-by: Mads Kiilerich <mads@kiilerich.com>
When generating a configuration file using 'kallithea-cli config-create', it is
probably using the right Python interpreter, so fill in the current Python
executable as 'git_hook_interpreter' in the generated file.
There should thus rarely be any need to configure this manually, and issue #333
will *really* be fixed.
As this causes an absolute path to be encoded inside the ini file, moving
the virtualenv will require updating this path.
For development.ini we do not want to hardcode any path and are happy to leave
it using the old heuristics at runtime.
Suggested-by: Mads Kiilerich <mads@kiilerich.com>
aa17c7a1b8a5 aa17c7a1b8a5 8d065db04909 8d065db04909 8d065db04909 aa17c7a1b8a5 5ae8e644aa88 8d065db04909 03bbd33bc084 03bbd33bc084 5ae8e644aa88 5ae8e644aa88 8d065db04909 aa17c7a1b8a5 5ae8e644aa88 8d065db04909 aa17c7a1b8a5 8d065db04909 5ae8e644aa88 8d065db04909 aa17c7a1b8a5 8d065db04909 8d065db04909 5ae8e644aa88 8d065db04909 aa17c7a1b8a5 8d065db04909 8d065db04909 | .. _locking:
==================
Repository locking
==================
Kallithea has a *repository locking* feature, disabled by default. When
enabled, every initial clone and every pull gives users (with write permission)
the exclusive right to do a push.
When repository locking is enabled, repositories get a ``locked`` flag.
The hg/git commands ``hg/git clone``, ``hg/git pull``,
and ``hg/git push`` influence this state:
- A ``clone`` or ``pull`` action locks the target repository
if the user has write/admin permissions on this repository.
- Kallithea will remember the user who locked the repository so only this
specific user can unlock the repo by performing a ``push``
command.
- Every other command on a locked repository from this user and every command
from any other user will result in an HTTP return code 423 (Locked).
Additionally, the HTTP error will mention the user that locked the repository
(e.g., “repository <repo> locked by user <user>”).
Each repository can be manually unlocked by an administrator from the
repository settings menu.
|