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

Fork of rhodecode-enterprise-ce

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
sec-instance-basics.rst
31 lines | 1.2 KiB | text/x-rst | RstLexer
/ docs / admin / sec-instance-basics.rst
History | Annotation | Raw |Copy content |Copy permalink

3 Basic User Security Steps

By implementing the following user configuration tasks, you will help to secure your |RCE| instances.

Define the Instance Wide Default User

The default user settings are applied across the whole instance. You should define the default user so that newly created users immediately have permission settings attached to their profile. For more information about defining the default user settings, see the :ref:`default-perms` section.

Configure Specific User Groups

By defining user groups, it allows you to put users into them and have the group permissions applied to their profile. For more information about defining the default user settings, see the :ref:`user-admin-set` section.

Define the Default User in Each Group

Apart from the system wide user permissions, each user group can apply its settings to the default user permissions within the scope of the group. To set the default user's permissions inside a user group, see the :ref:`permissions-info-repo-group-access` section.