##// END OF EJS Templates
u » pc » rhodecode-enterprise-ce-fork-pc
RSS

Fork of rhodecode-enterprise-ce

scm-app: allow to set documented pyro4 as scm_app_implementation....
scm-app: allow to set documented pyro4 as scm_app_implementation. The documented ini setting allows to set pyro4 as scm_app, while the backend code crashes on import of pyro4 module. This change allows to configure the app based on the .ini docs. if we pass pyro4 as backedn, we simply skip import and use the default pyro4 scm_app
marcink - - Load All Authors

File last commit:

r1:854a839a default
r632:064401fe 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.