##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
svn: Ignore the content length header from response, fixes #4112...
svn: Ignore the content length header from response, fixes #4112 In case of compressed responses from apache(mod_dav_svn) we can not use the Content-Length header in our own response. The content is automatically decompressed by the requests library and therefore the content length differs. This results in errors when doing e.g. a svn checkout: "svn: E120106: ra_serf: The server sent a truncated HTTP response body."
marcink - - Load All Authors

File last commit:

r1:854a839a default
r473:7e153d56 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.