- Timestamp:
- 08/04/2004 05:25:48 AM (20 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 95c3dc2
- Parents:
- da4aff6
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
server/other/svnserver.xml
rda4aff6 r7afc6e2 14 14 <title>Running a Subversion Server</title> 15 15 <para>This section will describe how to set up, administer and secure 16 a <application>Subversion</application> server. Since 17 <application>Subversion</application> is intended to replace 18 <acronym>CVS</acronym>, it may surprise you how very different the setup 19 of a <application>Subversion</application> repository is compared to a 20 <acronym>CVS</acronym> repository.</para> 16 a <application>Subversion</application> server.</para> 21 17 22 18 <sect3><title><application>Subversion server</application> dependencies</title> … … 30 26 <title>Setting up a <application>Subversion</application> server.</title> 31 27 32 <para>A <application>Subversion</application> server will be set up using 33 OpenSSH as the remote access method.</para> 28 <para>The following instructions will install a 29 <application>Subversion</application> server, which will be set up to 30 use <application>OpenSSH</application> as the secure remote access method, with 31 <command>svnserve</command> available for anonymous access.</para> 34 32 35 33 <para>Configuration of the <application>Subversion</application> server … … 72 70 73 71 <note><para>If you use <application>apache</application> for working with 74 the repository over the web, even for anonymous access, you should wrap72 the repository over http, even for anonymous access, you should wrap 75 73 <application>apache</application> in a similar script.</para></note> 76 74 … … 109 107 110 108 <para>Now go ahead and change owner and group information on the 111 repository, a dd your normal user to the svn and svntest groups:</para>109 repository, and add your normal user to the svn and svntest groups:</para> 112 110 113 111 <screen><userinput><command>chown -R svn:svntest /srv/svn/repositories/svntest && … … 117 115 118 116 <para>svntest is the group assigned to the svntest repository. As 119 mentioned earlier, this eases administration of multiple repositories. 120 Going forward, you'll need to add your regular user, and any additional 121 users that you wish to have write access to the repository, to the svn and 117 mentioned earlier, this eases administration of multiple repositories 118 when using <application>OpenSSH</application> for authentication. Going 119 forward, you'll need to add your regular user, and any additional users 120 that you wish to have write access to the repository, to the svn and 122 121 svntest groups.</para> 123 122 … … 131 130 132 131 <para>Now, go ahead and return to your normal user account, and take a look at 133 your new repository using svnlook:</para>132 your new repository using <command>svnlook</command>:</para> 134 133 135 134 <screen><userinput><command>svnlook tree /srv/svn/repositories/svntest/</command></userinput></screen> 136 135 137 136 <note><para>You may need to logout and back in again to refresh your group 138 memberships. ' su <replaceable>[username]</replaceable>' should work139 around this as well.</para></note>137 memberships. '<command>su <replaceable>[username]</replaceable></command>' 138 should work around this as well.</para></note> 140 139 141 140 </sect3> … … 143 142 <sect3><title>3. Configure the server</title> 144 143 145 <para> These instructions will configure the server to use only ssh146 for write permission, and provide anonymous read-only permission. There 147 a re several other ways to provide access to the repository. These148 additional configurations are best explained at149 <ulink url="http://svnbook.red-bean.com/" />.</para>144 <para>As mentioned previously, these instructions will configure the 145 server to use only ssh for write access to the repository and to provide 146 anonymous access using <command>svnserve</command>. There are several other 147 ways to provide access to the repository. These additional configurations 148 are best explained at <ulink url="http://svnbook.red-bean.com/" />.</para> 150 149 151 150 <para>Access configuration needs to be done for each repository. Create … … 173 172 <application>xinetd</application> process. Alternately, you can use a 174 173 bootscript to start the service at startup.</para> 174 175 <note><para>If you do not wish to provide anonymous access to your svn 176 repositories or use <command>svnserve</command>'s built-in 177 authentication, you do not need to run 178 <command>svnserve</command>.</para></note> 175 179 176 180 <para>If you use <application>inetd</application>, add a line to your
Note:
See TracChangeset
for help on using the changeset viewer.