- Timestamp:
- 05/29/2016 09:10:18 PM (8 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- c5ebc8ac
- Parents:
- c219568
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/svnserver.xml
rc219568 r1e5a9a41 21 21 <para>This section will describe how to set up, administer and secure 22 22 a <application>Subversion</application> server.</para> 23 24 <!-- <note>25 <para>The default build instructions for26 <application>Subversion</application> disabled the27 <application>Berkeley DB</application> repository back-end due to the28 errors encountered in the test suite while building the29 <xref linkend="subversion"/> package. This should not present a30 functionality issue as the FSFS repository back-end is now the default,31 and recommended by the <application>Subversion</application> development32 team.</para>33 34 <para>If you have existing repositories based on a35 <application>Berkeley DB</application> back-end and you followed the36 BLFS instructions for building <application>Subversion</application>,37 you'll need to dump the databases, create new repositories using the38 FSFS back-end, then then reload the data into the new repositories.39 Instructions for performing these operations can be found at <ulink40 url="http://svnbook.red-bean.com/en/1.1/ch05s03.html#svn-ch-5-sect-3.5"/>.41 </para>42 </note> -->43 23 44 24 <bridgehead renderas="sect3">Subversion Server Dependencies</bridgehead> … … 112 92 <title>2. Create a Subversion repository.</title> 113 93 114 <para>With subversion-1.1.0 and greater, a new type of repository 115 data-store is available, FSFS. There is a tradeoff for speed with 116 the new backend, however, the repository can now be placed on a 117 network mount, and any corruption does not require an admin to 118 recover the repository. For more information and comparison between 119 FSFS and BDB, see <ulink 120 url="http://svnbook.red-bean.com/svnbook-1.1/ch05.html#svn-ch-5-sect-1.2.A"/>. 94 <para> 95 There are several ways to set up a subversion repository. It is 96 recommended to have a look at the <ulink 97 url="http://svnbook.red-bean.com/nightly/en/svn.reposadmin.html">SVN 98 Book</ulink> corresponding chapter. A basic repository can be set up 99 with the instructions below. 121 100 </para> 122 101 123 <para>Create a new <application>Subversion</application> repository with 124 the following commands:</para> 102 <para> 103 Create a new <application>Subversion</application> repository with 104 the following commands (as the <systemitem class="username">root 105 </systemitem> user): 106 </para> 125 107 126 108 <screen role="root"><userinput>install -v -m 0755 -d /srv/svn && 127 109 install -v -m 0755 -o svn -g svn -d /srv/svn/repositories && 128 svnadmin create --fs-type fsfs/srv/svn/repositories/svntest</userinput></screen>110 svnadmin create /srv/svn/repositories/svntest</userinput></screen> 129 111 130 112 <para>Now that the repository is created, it should be populated with 131 withsomething useful. You'll need to have a predefined directory113 something useful. You'll need to have a predefined directory 132 114 layout set up exactly as you want your repository to look. For 133 115 example, here is a sample BLFS layout setup with a root of … … 226 208 <sect3 id="svnserver-init"> 227 209 <title>4. Starting the Server</title> 228 <!-- 229 <para>There are a couple of ways to start <command>svnserve</command>. 230 The most common way is to start it as an <command>inetd</command> or 231 <command>xinetd</command> process. Alternately, you can use a 232 bootscript to start the service at startup.</para> 233 234 <note> 235 <para>If you do not wish to provide anonymous access to your svn 236 repositories or use <command>svnserve</command>'s built-in 237 authentication, you do not need to run 238 <command>svnserve</command>.</para> 239 </note> 240 241 <para>If you use <command>inetd</command>, add a line to 242 <filename>/etc/inetd.conf</filename> using the following 243 commands:</para> 244 245 <indexterm zone="svnserver svnserver-init"> 246 <primary sortas="e-etc-inetd.conf">/etc/inetd.conf</primary> 247 </indexterm> 248 249 <screen role="root"><userinput>cat >> /etc/inetd.conf << "EOF" 250 <literal>svn stream tcp nowait svn /usr/bin/svnserve svnserve -i</literal> 251 EOF</userinput></screen> 252 253 <para>If you use <command>xinetd</command>, the following command will 254 create the <application>Subversion</application> server file as 255 <filename>/etc/xinetd.d/svn</filename>:</para> 256 257 <indexterm zone="svnserver svnserver-init "> 258 <primary sortas="e-etc-xinetd.d-svn">/etc/xinetd.d/svn</primary> 259 </indexterm> 260 261 <screen role="root"><userinput>cat >> /etc/xinetd.d/svn << "EOF" 262 <literal># Begin /etc/xinetd.d/svn 263 264 service svn 265 { 266 port = 3690 267 socket_type = stream 268 protocol = tcp 269 wait = no 270 user = svn 271 server = /usr/bin/svnserve 272 server_args = -i -r /srv/svn/repositories 273 } 274 275 # End /etc/xinetd.d/svn</literal> 276 EOF</userinput></screen> --> 277 278 <para>To start the server at boot time, install the svn bootscript included 279 in the <xref linkend="bootscripts"/> package.</para> 210 211 <para>To start the server at boot time, install the svn bootscript 212 included in the <xref linkend="bootscripts"/> package.</para> 280 213 281 214 <indexterm zone="svnserver svnserver-init">
Note:
See TracChangeset
for help on using the changeset viewer.