##// END OF EJS Templates
shadow-repos: use safer way to destroy shadow repositories....
shadow-repos: use safer way to destroy shadow repositories. we had reported errors on removal of shadow repos. Not reproduced, however suspecting are filesystem sync/symlink race-conditions on shared storage. End result were existing shadow-repo directories that tricked rhodecode into thinking shadow repos is existing, but infact it was a dummy structure semi-removed. Using shutil.move we ENSURE rhodecode doesn't read those back even if removal fails.

File last commit:

r1:854a839a default
r2777:f1cc2e3d default
Show More
repo-locking.rst
14 lines | 586 B | text/x-rst | RstLexer
project: added all source files and assets
r1 .. _repo-locking:
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`