##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
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.
marcink - - Load All Authors

File last commit:

r1:854a839a default
r2777:f1cc2e3d default
Show More
setting-repo-perms.rst
26 lines | 880 B | text/x-rst | RstLexer
/ docs / admin / setting-repo-perms.rst
History | Annotation | Raw |Copy content |Copy permalink

Repository Administration

Repository permissions in |RCM| can be managed in a number of different ways. This overview should give you an insight into how you could adopt particular settings for your needs:

  • Global |repo| permissions: This allows you to set the default permissions for each new |repo| created within |RCM|, see :ref:`repo-default-ref`. All |repos| created will inherit these permissions unless explicitly configured.
  • Individual |repo| permissions: To set individual |repo| permissions, see :ref:`set-repo-perms`.
  • Repository Group permissions: This allows you to define the permissions for a group, and all |repos| created within that group will inherit the same permissions.