{"id":288,"date":"2026-10-13T09:11:28","date_gmt":"2026-10-13T09:11:28","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2010\/11\/26\/subversions-components\/"},"modified":"2026-10-13T09:11:28","modified_gmt":"2026-10-13T09:11:28","slug":"subversions-components","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/subversions-components\/","title":{"rendered":"Subversion Components Explained: What Each SVN Tool Does and When to Use It"},"content":{"rendered":"\n

Originally published on 2010-11-26; fully revised and updated.<\/em><\/p>\n\n\n\n

Subversion includes more than just the svn<\/code> client binary. If you are developing, administering repositories, or setting up network access, knowing which component to use prevents mistakes and speeds up troubleshooting. This guide explains the core Subversion components, how they fit together, and the commands you are most likely to run.<\/p>\n\n\n\n

\"Subversion<\/figure>\n\n\n\n

Subversion components at a glance<\/h2>\n\n\n\n

The original post listed the primary binaries and modules commonly installed with Subversion. The table below summarizes what each one is for.<\/p>\n\n\n\n

Component<\/th>Type<\/th>Primary purpose<\/th><\/tr><\/thead>
svn<\/code><\/td>Client CLI<\/td>Day-to-day version control operations from a working copy<\/td><\/tr>
svnversion<\/code><\/td>Client utility<\/td>Reports working copy revision state<\/td><\/tr>
svnlook<\/code><\/td>Repository inspection utility<\/td>Reads repository data directly (no working copy required)<\/td><\/tr>
svnadmin<\/code><\/td>Repository admin utility<\/td>Creates, maintains, backs up, and repairs repositories<\/td><\/tr>
mod_dav_svn<\/code><\/td>Apache module<\/td>Publishes repositories over HTTP or HTTPS<\/td><\/tr>
svnserve<\/code><\/td>Server daemon<\/td>Publishes repositories using the Subversion network protocol<\/td><\/tr>
svndumpfilter<\/code><\/td>Stream utility<\/td>Filters repository dump streams by path<\/td><\/tr>
svnsync<\/code><\/td>Replication utility<\/td>Incrementally mirrors one repository to another<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

How these components fit together<\/h2>\n\n\n\n

In a typical setup, developers use client commands, repositories are served via Apache or svnserve<\/code>, and admin tools handle backup, inspection, and replication.<\/p>\n\n\n\n

\nflowchart LR\n    Dev[Developer] --> Cli[svn client]\n    Cli -->|https| Apache[Apache mod_dav_svn]\n    Cli -->|svn or svn+ssh| Serve[svnserve]\n    Apache --> Repo[(Subversion repository)]\n    Serve --> Repo\n    Look[svnlook] --> Repo\n    Admin[svnadmin] --> Repo\n    Repo --> Dump[Repository dump]\n    Dump --> Filter[svndumpfilter]\n    Repo --> Mirror[svnsync job]\n<\/pre>\n\n\n\n
Client and inspection commands you will run most often<\/h2>\n\n\n\n
These examples cover common developer and read-only inspection tasks. Adjust repository URLs and filesystem paths to your environment.<\/p>\n\n\n
# Working copy operations<\/span>\nsvn checkout https:\/\/svn.example.com\/svn\/project project-wc<\/span>\ncd project-wc\nsvn update\nsvn status\nsvnversion .\n\n# Repository inspection without checkout<\/span>\nsvnlook youngest \/srv\/svn\/project\nsvnlook tree \/srv\/svn\/project | head<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Administration, dump filtering, and mirroring<\/h2>\n\n\n\n
Use administrative tools directly on repository storage paths or repository URLs, not inside a working copy. For mirroring with svnsync<\/code>, destination-side hook setup is typically required before synchronization.<\/p>\n\n\n
# Create and back up a repository<\/span>\nsvnadmin create \/srv\/svn\/project\nsvnadmin hotcopy \/srv\/svn\/project \/backups\/project-hotcopy\nsvnadmin dump \/srv\/svn\/project > \/backups\/project.dump\n\n# Filter paths from a dump stream<\/span>\nsvndumpfilter include<\/span> trunk branches\/team-a < \/backups\/project.dump > \/backups\/project-filtered.dump\n\n# Initialize and run a mirror<\/span>\nsvnsync init file:\/\/\/srv\/svn\/project-mirror https:\/\/svn.example.com\/svn\/project<\/span>\nsvnsync sync file:\/\/\/srv\/svn\/project-mirror<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Serving repositories: Apache module vs svnserve<\/h2>\n\n\n\n
Option<\/th>Protocol and URL style<\/th>Strengths<\/th>Trade-offs<\/th><\/tr><\/thead>
mod_dav_svn<\/code> with Apache<\/td>HTTP or HTTPSExample: https:\/\/svn.example.com\/svn\/project<\/code><\/td>Works with Apache ecosystem (TLS termination, auth modules, reverse proxies)<\/td>More moving parts to configure and maintain<\/td><\/tr>
svnserve<\/code> daemon<\/td>svn protocolExample: svn:\/\/svn.example.com\/project<\/code><\/td>Lightweight and straightforward deployment<\/td>Different auth and transport model than web-based access<\/td><\/tr>
svnserve<\/code> via SSH tunnel<\/td>svn+ssh protocolExample: svn+ssh:\/\/alice@svn.example.com\/project<\/code><\/td>Uses SSH accounts and encrypted transport<\/td>Operational model depends on SSH account management<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n
# Start svnserve as a daemon, rooted at \/srv\/svn<\/span>\nsvnserve -d -r \/srv\/svn<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Common pitfalls<\/h2>\n\n\n\n
  • Running svnadmin<\/code> or other repository-admin commands against a working copy path instead of repository storage.<\/li>
  • Assuming svnversion<\/code> is the same as a single global repository revision; mixed-revision working copies can report ranges or flags.<\/li>
  • Editing repository internals directly instead of using supported tools such as svnadmin<\/code> and svnlook<\/code>.<\/li>
  • Setting up svnsync<\/code> without destination-side hook prerequisites.<\/li>
  • Choosing an access method without planning authentication, authorization, and transport security requirements.<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"
    Subversion ships with multiple command-line tools and server modules, each designed for a specific repository task. This updated guide maps the components, shows how they work together, and provides practical command examples.<\/p>\n","protected":false},"author":1,"featured_media":4346,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[23],"tags":[246,4064,4069,394,4062,4063,395,4061,4065,4068,4071,4067,4070,4072,4066],"class_list":["post-288","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-svnsubversion","tag-components","tag-introduction-of-svn-components","tag-mod_dav_svn","tag-subversion","tag-subversion-components-overview","tag-subversion-different-component-introduction","tag-svn","tag-svn-components","tag-svn-components-list","tag-svnadmin","tag-svndumpfilter","tag-svnlook","tag-svnserve","tag-svnsync","tag-svnversion"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/288","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=288"}],"version-history":[{"count":3,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/288\/revisions"}],"predecessor-version":[{"id":79125,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/288\/revisions\/79125"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media\/4346"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=288"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=288"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=288"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}