kallithea Files · docs/usage/locking.rst

Files @ 42718729687e

Branch filter:

Location: kallithea/docs/usage/locking.rst

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

Thomas De Schampheleire

style: use npm less to generate kallithea stylesheet style.css from style.less

This is a minimal change to introduce less as framework to generate our
stylesheet. The input less file is currently the same as the original css
stylesheet, so that the delta between the input style.less and the output
style.css is zero.

To regenerate style.css from style.less, run:

npm --prefix kallithea/public/less install
npm --prefix kallithea/public/less run less

These changes are based on work by Dominik Ruf.

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