kallithea Files · docs/usage/locking.rst

Files @ c5512c9d2118

Branch filter:

Location: kallithea/docs/usage/locking.rst

c5512c9d2118 1.1 KiB text/prs.fallenstein.rst Show Annotation Show as Raw Download as Raw

Karl Goetz

docs/vcs_support: add information on importing repositories

This change directly relates to issue #254.

Some rework of the original patch done by Thomas De Schampheleire:
- generalize to cover both Mercurial and Git
- simplify instructions for importing via filesystem: don't impose a certain
flow as it depends on different factors: are the repos already present on
the machine, are they organized in a flat hierarchy or already in a more
complex one, ...
- invalidating cache while rescanning should not be needed when adding new
repositories

.. _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.