##// END OF EJS Templates
upstream » kallithea
RSS

Clone from https://kallithea-scm.org/repos/kallithea

TurboGears2 migration: update ini files for error email settings...
TurboGears2 migration: update ini files for error email settings Error emails are now handled by backlash, which is configured through TurboGears2's ErrorReporter. ErrorReporter expects different configuration key names than Pylons did, moreover under a new 'trace_errors' namespace. Since some of the email-related settings are shared between application and error emails, we cannot just rename the existing settings (it would be very odd to have application settings under a 'trace_errors' namespace). Requiring the user to duplicate its settings is also undesirable. Instead, use 'get' to populate the trace_errors namespace based on the existing settings we already had. Unfortunately, 'get' expects the setting to be actually present, so we need to provide an out-of-the-box value for the error-related email settings or there will be an error at startup. We use empty values because there is no realistic default value we can provide.
Søren Løvborg - - Load All Authors

File last commit:

r5425:5ae8e644 default
r6529:b4c27fe6 default
Show More
locking.rst
28 lines | 1.1 KiB | text/x-rst | RstLexer
/ docs / usage / locking.rst
History | Annotation | Raw |Copy content |Copy permalink

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.