Tutorial: mention shared repository management.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Junio C Hamano committed
Dec 23, 2005 at 15:27 UTC
b74ed497350844c3c9fc77c68de3843392086e9b
1 file changed
+18
Documentation/tutorial.txt
+18
@@ -1695,6 +1695,24 @@ You still need to create UNIX user accounts for each developer,
1695
and put them in the same group. Make sure that the repository
1696
shared among these developers is writable by that group.
1697
1698
+. Initializing the shared repository with `git-init-db --shared`
1699
+helps somewhat.
1700
+
1701
+. Run the following in the shared repository:
1702
++
1703
+------------
1704
+$ chgrp -R $group repo.git
1705
+$ find repo.git -type d -print | xargs chmod ug+rwx,g+s
1706
+$ GIT_DIR=repo.git git repo-config core.sharedrepository true
1707
+------------
1708
+
1709
+The above measures make sure that directories lazily created in
1710
+`$GIT_DIR` are writable by group members. You, as the
1711
+repository administrator, are still responsible to make sure
1712
+your developers belong to that shared repository group and set
1713
+their umask to a value no stricter than 027 (i.e. at least allow
1714
+reading and searching by group members).
1715
+
1716
You can implement finer grained branch policies using update
1717
hooks. There is a document ("control access to branches") in
1718
Documentation/howto by Carl Baldwin and JC outlining how to (1)