##// END OF EJS Templates
settings: re-use attached request global config for performance...
settings: re-use attached request global config for performance - since we *always* generate a global config and register it into request make use of it, and not rely on the get_all_settings heavy logic that makes it slow to fetch because of cache checks. Within single request we're fine to re-use it when ever request attribute is available

File last commit:

r1:854a839a default
r4200:007322e6 stable
Show More
repo-locking.rst
14 lines | 586 B | text/x-rst | RstLexer

Repository Locking

Repository locking means that when a user pulls from a |repo|, only a push by that user will unlock it. This allows an Admin to pull from a |repo| and ensure that no changes can be introduced. You need Admin access to the |repo| to enable |repo| locking. To enable |repo| locking, use the following steps.

  1. From the |RCE| interface, select :menuselection:`Admin --> Repositories`, then :guilabel:`Edit` beside the |repo| you wish to lock.
  2. From the left-hand pane, select :menuselection:`Advanced --> Lock Repository`