Files
@ 9885bbacf99c
Branch filter:
Location: kallithea/docs/usage/locking.rst - annotation
9885bbacf99c
1.1 KiB
text/prs.fallenstein.rst
.hgignore: Add .eggs/ and tarballcache/
Setuptools >= 7.0 and .eggs is created and populated with eggs if setup.py has
setup_requires of packages that are not installed and setuptools has to
download them to satisfy the requirements. See
https://bitbucket.org/pypa/setuptools/pull-request/97/cache-eggs-required-for-building-in-eggs/diff#
tarballcache comes from test.ini : archive_cache_dir = %(here)s/tarballcache
Setuptools >= 7.0 and .eggs is created and populated with eggs if setup.py has
setup_requires of packages that are not installed and setuptools has to
download them to satisfy the requirements. See
https://bitbucket.org/pypa/setuptools/pull-request/97/cache-eggs-required-for-building-in-eggs/diff#
tarballcache comes from test.ini : archive_cache_dir = %(here)s/tarballcache
aa17c7a1b8a5 aa17c7a1b8a5 8d065db04909 8d065db04909 8d065db04909 aa17c7a1b8a5 8d065db04909 8d065db04909 03bbd33bc084 03bbd33bc084 8d065db04909 8d065db04909 8d065db04909 aa17c7a1b8a5 8d065db04909 8d065db04909 aa17c7a1b8a5 8d065db04909 8d065db04909 8d065db04909 aa17c7a1b8a5 8d065db04909 8d065db04909 8d065db04909 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`` state that
can be true or false. The hg/git commands ``hg/git clone``, ``hg/git pull``,
and ``hg/git push`` influence this state:
- A ``clone`` or ``pull`` action on the repository locks it (``locked=true``)
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 (``locked=false``) 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 includes 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.
|