Files @ 89e50be94fcb
Branch filter:

Location: kallithea/docs/usage/locking.rst - annotation

89e50be94fcb 1.1 KiB text/prs.fallenstein.rst Show Source Show as Raw Download as Raw
Thomas De Schampheleire
i18n: remove old English translation file

Under TurboGears2, automatic user language detection based on browser settings
is enabled by default. If a user has 'English' as preferred language in the
browser, then the old English .mo file with a few dummy entries would be read
and used first, before trying the language configured in the Kallithea .ini
file (e.g. French). This renders a mix of languages in the UI ... which is
unexpected.

The hiding of configured translation is fixed by removing the old english
translationfile. It was preserved via commit 7d6c4bd58abd when removing all
other .mo files. The next release will require major config changes anyway, and
we don't try to be backwards compatible.
.. _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.