[svnbook] r5117 committed - trunk/en/book/ch06-server-configuration.xml

[C. Michael Pilato]

Review comments inline:

On Wed, Mar 2, 2016 at 10:22 AM, <lyalyakin at users.sourceforge.net> wrote:

> Revision: 5117
>           http://sourceforge.net/p/svnbook/source/5117
>
>
[...]


> Modified: trunk/en/book/ch06-server-configuration.xml
> ===================================================================
> --- trunk/en/book/ch06-server-configuration.xml 2016-03-02 13:41:52 UTC
> (rev 5116)
> +++ trunk/en/book/ch06-server-configuration.xml 2016-03-02 15:22:08 UTC
> (rev 5117)
> @@ -2838,6 +2838,56 @@
>
>        </sect3>
>
> +      <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> -->
> +      <sect3 id="svn.serverconfig.httpd.authz.inrepo-authz">
> +        <title>Versioned In Repository Authorization Files</title>
> +
> +        <para>Beginning with Subversion 1.8, authz files can be stored
> +          inside a Subversion repository.  It is possible to store the
> +          authorization file in the same repository to which the
> +          access rules are being applied or another repository.  This
> +          approach enables versioning features of Subversion for
> +          the path-based authorization.</para>
>

... the path-based authorization configuration.

(It's not the authorization that's being versioned.  It's the configuration
files that govern said authorization.)


> +
> +        <para>Both <literal>AuthzSVNAccessFile</literal> and
> +          <literal>AuthzSVNReposRelativeAccessFile</literal> configuration
> +          directives allow to specify in repo authorization file absolute
> +          or relative URL via local <literal>file://</literal> access
> method,
> +          but not <literal>svn://</literal> and <literal>http://
> </literal>
> +          or <literal>https://</literal> methods.</para>
>

This paragraph is a bit confusing.  There's no such thing as a relative
file:// URL.  The presence of the protocol at all ensures that the URL is
absolute.  Also, it's best not to bother naming the other protocols because
a) the list is incomplete (what about svn+ssh:// or a custom protocol?) and
b) it confuses the matter.  Just say that we support relative URLs and
absolute file:/// URLs.


> +
> +        <para>For example, it is possible to specify absolute URL to in
> +          repository authz file as shown in
>

...specify an absolute URL to an in-repository access file as shown in...


> +          <xref
> linkend="svn.serverconfig.httpd.authz.inrepo-authz.ex-1"/>.</para>
> +
> +        <example id="svn.serverconfig.httpd.authz.inrepo-authz.ex-1">
> +          <title>Using single versioned in repo authz file</title>
> +          <programlisting>
> +<Location /repos>
> +  DAV svn
> +  SVNParentPath /var/svn
> +  AuthzSVNAccessFile file:///var/svn/authzrepo/authz
> +</Location>
> +</programlisting>
> +        </example>
> +
> +        <para>You can also specify relative URL to in repository authz
> +          file as shown in
>

...specify a relative URL to an in-repository access file, demonstrated
in...

(Besides the grammar edit to include missing articles, it's best in prose
to not be too repetitive.  Thus, "demonstrated in" as opposed to another
instance of "as shown in".)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.red-bean.com/pipermail/svnbook-dev/attachments/20160303/9201640a/attachment-0002.html>