# HG changeset patch # User Paul Crowley # Date 1255599005 -3600 # Node ID 2dbaddde1fd5d6b2b7a5bb9c63662eef683fd182 # Parent afb1d57ca9f7a8bbff5a6e2c2393919cac879d48 programlisting also needs no initial blank lines diff -r afb1d57ca9f7 -r 2dbaddde1fd5 doc/manual.docbook --- a/doc/manual.docbook Thu Oct 15 10:24:50 2009 +0100 +++ b/doc/manual.docbook Thu Oct 15 10:30:05 2009 +0100 @@ -152,8 +152,7 @@ class='directory'>keys/widget/pat directory in hgadmin. Now mercurial-server knows about Pat's key, but will give Pat no access to anything because the key is not under either keys/root or keys/users. To grant this key access, we must give mercurial-server a new access rule, so we create a file in hgadmin called access.conf, with the following contents: - - write repo=widget user=widget/** +write repo=widget user=widget/** Pat will have read and write access as soon as we add, commit, and push these files. @@ -161,8 +160,7 @@ Each line of access.conf has the following syntax: - -rule condition condition... +rule condition condition... Blank lines and lines that start with # are ignored. Rule is one of @@ -187,10 +185,9 @@ By default, /etc/mercurial-server/access.conf has the following rules: - - init user=root/** - deny repo=hgadmin - write user=users/** +init user=root/** +deny repo=hgadmin +write user=users/** These rules ensure that root users can do any operation on any repository, that no other users can access the hgadmin repository, and that those with keys in keys/users can read or write to any repository but not create repositories. @@ -318,9 +315,8 @@ rule and a file condition: any user who has access to a repository can read all of it and its full history. Such a rule can only have the effect of masking a later "write" rule, as in this example: - - read repo=specialrepo file=dontwritethis - write repo=specialrepo +read repo=specialrepo file=dontwritethis +write repo=specialrepo allows all users to read specialrepo, and to write to all files @@ -338,18 +334,16 @@ to write to all the files they can write to on any branch. In other words, something like this will have the intended effect: - - write user=docs/* branch=docs file=docs/* +write user=docs/* branch=docs file=docs/* But something like this will not have the intended effect; it will effectively allow these users to write to any file on any branch, by writing it to "docs" first: - - write user=docs/* branch=docs - write user=docs/* file=docs/* - read user=docs/* +write user=docs/* branch=docs +write user=docs/* file=docs/* +read user=docs/*