equal
deleted
inserted
replaced
14 <para> |
14 <para> |
15 mercurial-server gives your developers remote read/write access to |
15 mercurial-server gives your developers remote read/write access to |
16 centralized <link xlink:href="http://hg-scm.org/">Mercurial</link> |
16 centralized <link xlink:href="http://hg-scm.org/">Mercurial</link> |
17 repositories using SSH public key authentication; it provides convenient |
17 repositories using SSH public key authentication; it provides convenient |
18 and fine-grained key management and access control. |
18 and fine-grained key management and access control. |
|
19 It provides access control for <link xlink:href="http://mercurial.selenic.com/wiki/Phases">phases</link> |
|
20 move (from "draft" to "public"). |
19 </para> |
21 </para> |
20 <para> |
22 <para> |
21 Though mercurial-server is currently targeted at Debian-based systems such |
23 Though mercurial-server is currently targeted at Debian-based systems such |
22 as Ubuntu, other users have reported success getting it running on other |
24 as Ubuntu, other users have reported success getting it running on other |
23 Unix-based systems such as Red Hat. Running it on a non-Unix system such as |
25 Unix-based systems such as Red Hat. Running it on a non-Unix system such as |
177 Blank lines and lines that start with <code>#</code> are ignored. Rule is |
179 Blank lines and lines that start with <code>#</code> are ignored. Rule is |
178 one of |
180 one of |
179 </para> |
181 </para> |
180 <itemizedlist> |
182 <itemizedlist> |
181 <listitem> |
183 <listitem> |
182 <literal>init</literal>: allow reads, writes, and the creation of new repositories |
184 <literal>init</literal>: allow reads, writes, publish (move the phase |
183 </listitem> |
185 of a chageset to "public"), and the creation of new repositories |
184 <listitem> |
186 </listitem> |
185 <literal>write</literal>: allow reads and writes |
187 <listitem> |
|
188 <literal>publish</literal>: allow reads, writes and publish changesets |
|
189 </listitem> |
|
190 <listitem> |
|
191 <literal>write</literal>: allow reads and writes (ie. create draft changesets) |
186 </listitem> |
192 </listitem> |
187 <listitem> |
193 <listitem> |
188 <literal>read</literal>: allow only read operations |
194 <literal>read</literal>: allow only read operations |
189 </listitem> |
195 </listitem> |
190 <listitem> |
196 <listitem> |
191 <literal>deny</literal>: deny all requests |
197 <literal>deny</literal>: deny all requests |
192 </listitem> |
198 </listitem> |
193 </itemizedlist> |
199 </itemizedlist> |
|
200 <para> |
|
201 The distinction between "write" and "publish" access levels is only |
|
202 meaningful for non-publishing repositories, in which case, the |
|
203 "write" access level allows a user to push "draft" changesets, but |
|
204 not to change their phase to "public". This latter operation require |
|
205 the "publish" access level. |
|
206 </para> |
194 <para> |
207 <para> |
195 A condition is a globpattern matched against a relative path. The two most |
208 A condition is a globpattern matched against a relative path. The two most |
196 important conditions are |
209 important conditions are |
197 </para> |
210 </para> |
198 <itemizedlist> |
211 <itemizedlist> |