Implement * to mean any user or repo

[repo_shell.git] / README

diff --git a/README b/README
index 432904e8d1072763f25d481e7dd7eb8df6080690..b20c859eeac5465ccf3a8788723568e2e5b42d82 100644 (file)
--- a/README
+++ b/README
@@ -40,6 +40,7 @@ The /etc/repo_shell.cfg configuration file is straightforward:
     owner=repo
     git_root=/var/lib/git
     svn_root=/var/lib/svn/repositories
+    git_acl_file=/var/lib/git/.gitacls
 
 The owner field denotes the user that owns all repositories.  The git_root and
 svn_root fields identify the path to the respective repositories.  The latter
@@ -61,6 +62,9 @@ example:
     svnadmin create --fs-type fsfs <svn_root>/newreponame
     git --git-dir <git_root>/newrepopath.git init --bare
 
+Please see the svncreate for an example helper script for subversion repository
+creation.
+
 To use external viewers that directly interrogate the repository, the simplest
 solution is to have those viewers run as another user belonging to the owner's
 primary group.  In this case, in the examples above, a umask of 027 is
@@ -81,6 +85,9 @@ svnserve.conf set a global authz.conf file, using the standard hooks and
 activating svnperms.conf for branch-based commit control.  These are suggestions
 outside the scope of the repo_shell program itself.
 
-Access controls for git are envisioned to be incorporated into repo_shell.  They
-aren't at this time, and any developer has read-write access to any git
-repository.
+Access controls for git repositories uses a feature built-into repo_shell.
+The /etc/repo_shell.cfg file lists a core parameter git_acl_file, which
+should be set to the name of the git acl file.  A recommended name is
+/var/lib/git/.gitacls, with permissions 0400.  See git_acl.cfg.example for
+information on the format of this file, which is similar in concept, but
+different, than subversion's authz.conf file format.