##// 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
repo-perm-steps.rst
45 lines | 2.0 KiB | text/x-rst | RstLexer
/ docs / admin / repo-perm-steps.rst
History | Annotation | Raw |Copy content |Copy permalink

Setting Repository Permissions

To set the permissions on an individual |repo|, use the following steps:

  1. Open :menuselection:`Admin --> Repositories` and select :guilabel:`edit` beside the |repo| you wish to configure.
  2. On the |repo| settings page you will see a number of tabs. Exploring these you will find the following main configuration options for a |repo|.
  3. Once you make changes, select :guilabel:`Save`
  • :guilabel:`Repository group`: Lets you to add a |repo| to a |repo| group.
  • :guilabel:`Owner`: Lets you change the |repo| owner. Useful when users are moving roles within an organisation.
  • :guilabel:`Enable automatic locking`: For more information, see :ref:`repo-locking`
  • :guilabel:`User Access`: On the permissions tab you can add users, or user groups, and set the permissions each has for that |repo|.
  • :guilabel:`Invalidate repository cache`: On the Caches tab you can delete the |repo| cache, sometimes needed when mirroring.

Setting Repository Group Permissions

To set the permissions on a Repository Group, use the following steps:

  1. Open :menuselection:`Admin --> Repository groups` and select :guilabel:`edit` beside the |repo| you wish to configure.
  2. On the |repo| group settings page you will see a number of tabs. Exploring these you will find the following main configuration options:
  • :guilabel:`Owner`: Lets you change the group owner. Useful when users are moving roles within an organisation.
  • :guilabel:`Group parent`: Lets you add the |repo| group as a sub-group of a larger group, i.e. :guilabel:`QA-Repos >> QA-Repos-Berlin`
  • :guilabel:`Enable automatic locking`: For more information, see :ref:`repo-locking`
  • :guilabel:`User Access`: On the permissions tab you can add users, or user groups, and set the permissions each has for that |repo| group.
  • :guilabel:`Add Child Group`: Allows you to add sub-repository-groups that will all share the same permissions.