Context Navigation

-              r84e42bc
+              r01d5424
 <sect3><title><application>Subversion server</application> dependencies</title>
 <sect4><title>Required</title>
+<para><xref linkend="subversion"/> and <xref linkend="openssh"/></para></sect4>
+<para><xref linkend="subversion"/> and <xref linkend="openssh"/></para>
+</sect4>
 </sect3>
 …
 consists of the following steps:</para>
 <sect3><title>1.  Setup users, groups, and permissions</title>
+<sect3><title>1. Setup users, groups, and permissions</title>
 <para>You'll need to be user root for the initial portion of
 configuration.  Create the svn user and group with the following
+configuration. Create the svn user and group with the following
 commands:</para>
 …
 <para>If you plan to have multiple repositories, you should have a
 group dedicated to each repository for ease of administration.  Create
 the svntest group for our test repository and add the svn user to that
+group dedicated to each repository for ease of administration. Create
+the svntest group for the test repository and add the svn user to that
 group with the following commands:</para>
 …
 usermod -G svntest svn</command></userinput></screen>
 <para>Additionally you should set umask '002' while working with a
 repository so that all new files will be writable by owner and group.
 We'll make this mandatory by writing a wrapper script for
+<para>Additionally you should set <command>umask 002</command> while working
+with a repository so that all new files will be writable by owner and group.
+This is made mandatory by creating a wrapper script for
 <command>svn</command> and <command>svnserve</command>:</para>
 …
 chmod 0755 /usr/bin/svn{,serve}</command></userinput></screen>
+<note><para>If you use <application>apache</application> for working with
+the repository over http, even for anonymous access, you should wrap
+<application>apache</application> in a similar script.</para></note>
+</sect3>
+<sect3><title>2.  Create a <application>Subversion</application>
+<note><para>If you use <application>Apache</application> for working with
+the repository over <acronym>HTTP</acronym>, even for anonymous access, you
+should wrap <command>/usr/sbin/httpd</command> in a similar
+script.</para></note>
+</sect3>
+<sect3><title>2. Create a <application>Subversion</application>
 repository.</title>
 <para>Create a new <application>Subversion</application> repository with
 the following commands:</para>
 <screen><userinput><command>install -d -m0755 /srv &amp;&amp;
 install -d -m0755 -o svn -g svn /srv/svn/repositories &amp;&amp;
 …
 <para>Now that the repository is created, we need to populate it with
 something useful.  You'll need to have a predefined directory layout
 setup exactly as you want your repository to look.  For example, here
+something useful. You'll need to have a predefined directory layout
+setup exactly as you want your repository to look. For example, here
 is a sample BLFS layout setup with a root of <filename>svntest/</filename>.
 You'll need to setup a directory tree similar to the following:</para>
 …
              tags/            # Needed for tagging release points</screen>
 <para>Once you've created your directory layout as above, you are ready to
 do the initial import:</para>
+<para>Once you've created your directory layout as shown above, you are ready
+to do the initial import:</para>
 <screen><userinput><command>svn import -m "Initial import." \
 …
 usermod -G svn,svntest,<replaceable>[insert existing groups]</replaceable> <replaceable>[username]</replaceable></command></userinput></screen>
 <para>svntest is the group assigned to the svntest repository.  As
+<para>svntest is the group assigned to the svntest repository. As
 mentioned earlier, this eases administration of multiple repositories
 when using <application>OpenSSH</application> for authentication.  Going
+when using <application>OpenSSH</application> for authentication. Going
 forward, you'll need to add your regular user, and any additional users
 that you wish to have write access to the repository, to the svn and
 …
 <para>In addition, you'll notice that the new repository's
 <filename>db</filename> directory is set-groupID.  If the reasoning is
+<filename>db</filename> directory is set-groupID. If the reasoning is
 not immediately obvious, when using any external authentication method
 (such as ssh), the sticky bit is set so that all new files will be owned
 by the user, but group of svntest.  Anyone in the svntest group can
 create files, but still give the entire group write access to those
 files.  This avoids locking out other users from the repository.</para>
+(such as <command>ssh</command>), the sticky bit is set so that all new files
+will be owned by the user, but group of svntest. Anyone in the svntest group
+can create files, but still give the entire group write access to those
+files. This avoids locking out other users from the repository.</para>
 <para>Now, go ahead and return to your normal user account, and take a look at
 …
 <screen><userinput><command>svnlook tree /srv/svn/repositories/svntest/</command></userinput></screen>
 <note><para>You may need to logout and back in again to refresh your group
 memberships.  '<command>su <replaceable>[username]</replaceable></command>'
+<note><para>You may need to log out and back in again to refresh your group
+memberships. '<command>su <replaceable>[username]</replaceable></command>'
 should work around this as well.</para></note>
 </sect3>
 <sect3><title>3.  Configure the server</title>
+<sect3><title>3. Configure the server</title>
 <para>As mentioned previously, these instructions will configure the
+server to use only ssh for write access to the repository and to provide
+anonymous access using <command>svnserve</command>.  There are several other
+ways to provide access to the repository.  These additional configurations
+are best explained at <ulink url="http://svnbook.red-bean.com/" />.</para>
+<para>Access configuration needs to be done for each repository.  Create
+server to use only <command>ssh</command> for write access to the repository
+and to provide anonymous access using <command>svnserve</command>. There are
+several other ways to provide access to the repository. These additional
+configurations are best explained at
+<ulink url="http://svnbook.red-bean.com/"/>.</para>
+<para>Access configuration needs to be done for each repository. Create
 the <filename>svnserve.conf</filename> file for the svntest repository
 using the following commands:</para>
 …
 <command>EOF</command></userinput></screen>
 <para>There is not a lot to the configuration file at all.  You'll notice
 that only the general section is required.  Take a look at the
 <filename>svnserve.conf.default</filename> for information on using
+<para>There is not a lot to the configuration file at all. You'll notice
+that only the general section is required. Take a look at the
+<filename>svnserve.conf.default</filename> file for information on using
 <command>svnserve</command>'s built-in authentication method.</para>
 </sect3>
 <sect3><title>4.  Starting the server</title>
 <para>There are a couple of ways to start <command>svnserve</command>.  The
 most common way is to start it as an <application>inetd</application> or
 <application>xinetd</application> process.  Alternately, you can use a
+<sect3><title>4. Starting the server</title>
+<para>There are a couple of ways to start <command>svnserve</command>. The
+most common way is to start it as an <command>inetd</command> or
+<command>xinetd</command> process. Alternately, you can use a
 bootscript to start the service at startup.</para>
 …
 <command>svnserve</command>.</para></note>
 <para>If you use <application>inetd</application>, add a line to your
+<para>If you use <command>inetd</command>, add a line to
 <filename>/etc/inetd.conf</filename> using the following commands:</para>
 …
 <command>EOF</command></userinput></screen>
 <para>If you use <application>xinetd</application>, add the following
 lines to <filename>/etc/xinetd.conf</filename> file:</para>
+<para>If you use <command>xinetd</command>, add the following
+lines to the <filename>/etc/xinetd.conf</filename> file:</para>
 <screen><userinput><command>cat &gt;&gt; /etc/xinetd.conf &lt;&lt; "EOF"</command>

Note: See TracChangeset for help on using the changeset viewer.

Context Navigation

Changeset 01d5424 for server

Legend:

server/other/svnserver.xml

Download in other formats: