{"id":380,"date":"2026-10-14T01:20:59","date_gmt":"2026-10-14T01:20:59","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2014\/09\/25\/svn-server-setup\/"},"modified":"2026-10-14T01:20:59","modified_gmt":"2026-10-14T01:20:59","slug":"svn-server-setup","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/svn-server-setup\/","title":{"rendered":"SVN Server Setup with svnserve: Install, Secure, and Use a Subversion Repository"},"content":{"rendered":"\n

Originally published on 2014-09-25; fully revised and updated.<\/em><\/p>\n\n\n\n

If you need a lightweight Subversion server for a team or internal project, svnserve<\/strong> is the fastest path to get running. This guide walks administrators through installation, repository creation, access control, daemon startup, and first client operations with practical commands you can adapt to your environment.<\/p>\n\n\n\n

\"SVN<\/p>\n\n\n\n

What this guide sets up<\/h2>\n\n\n\n

By the end, you will have a working SVN repository served over svn:\/\/<\/strong> with user authentication and basic authorization controls.<\/p>\n\n\n\n

  • Install and verify Subversion tools (svn<\/code>, svnadmin<\/code>)<\/li>
  • Create a repository at a server path you control<\/li>
  • Configure svnserve.conf<\/code>, passwd<\/code>, and authz<\/code><\/li>
  • Start svnserve<\/code> as a daemon<\/li>
  • Import source and run checkout\/commit from clients<\/li><\/ul>\n\n\n\n

    SVN server setup workflow<\/h2>\n\n\n\n
    \nflowchart TD\n    A[Install Subversion] --> B[Create repository]\n    B --> C[Configure auth and access]\n    C --> D[Start svnserve daemon]\n    D --> E[Import initial code]\n    E --> F[Client checkout]\n    F --> G[Daily commit and update cycle]\n<\/pre>\n\n\n\n
    Install and verify Subversion<\/h2>\n\n\n\n
    Package commands vary by Linux distribution. Install Subversion, then verify both client and admin tools are available.<\/p>\n\n\n
    # Debian\/Ubuntu<\/span>\nsudo apt update\nsudo apt install subversion\n\n# RHEL\/CentOS Stream\/Fedora<\/span>\nsudo dnf install subversion\n\n# Older RHEL\/CentOS<\/span>\nsudo yum install subversion\n\n# Verify installation<\/span>\nsvn --version\nsvnadmin --version<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    Create repository storage<\/h2>\n\n\n\n
    Use a dedicated root directory for repositories. In this example, a single project repository is created at \/srv\/svn\/myproject<\/code>.<\/p>\n\n\n
    sudo mkdir -p \/srv\/svn\nsudo svnadmin create \/srv\/svn\/myproject\n\n# Inspect repository layout<\/span>\nls \/srv\/svn\/myproject<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    You should see standard Subversion repository directories such as conf<\/code>, db<\/code>, hooks<\/code>, and locks<\/code>.<\/p>\n\n\n\n
    Configure users and permissions<\/h2>\n\n\n\n
    Edit svnserve.conf<\/h3>\n\n\n\n
    Enable authenticated access and point svnserve to the password and authorization files.<\/p>\n\n\n
    # \/srv\/svn\/myproject\/conf\/svnserve.conf<\/span>\n[general]\nanon-access = none\nauth-access = write\npassword-db = passwd\nauthz-db = authz\nrealm = myproject<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    Define users and path-based authorization<\/h3>\n\n\n
    # \/srv\/svn\/myproject\/conf\/passwd<\/span>\n[users]\nalice = ChangeMeStrong1\nbob = ChangeMeStrong2\n\n# \/srv\/svn\/myproject\/conf\/authz<\/span>\n[\/]\nalice = rw\nbob = r<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    The original post used anonymous write access. For most environments, disable anonymous writes and require authenticated users.<\/p>\n\n\n\n
    Start svnserve and connect a client<\/h2>\n\n\n\n
    Start the daemon and set repository root with -r<\/code>. This keeps client URLs clean.<\/p>\n\n\n
    # Run svnserve in daemon mode with repository root<\/span>\nsvnserve -d -r \/srv\/svn\n\n# Client checkout example<\/span>\nsvn checkout svn:\/\/SVN_SERVER_IP\/myproject myproject<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    If you do not use -r<\/code>, clients usually need a longer URL path (for example, svn:\/\/SVN_SERVER_IP\/srv\/svn\/myproject<\/code>).<\/p>\n\n\n\n
    Access method<\/th>Example URL<\/th>Best for<\/th>Notes<\/th><\/tr><\/thead>
    file:\/\/<\/td>file:\/\/\/srv\/svn\/myproject<\/td>Local admin operations on server<\/td>No network service required<\/td><\/tr>
    svn:\/\/<\/td>svn:\/\/SVN_SERVER_IP\/myproject<\/td>Lightweight remote access via svnserve<\/td>What this guide configures<\/td><\/tr>
    https:\/\/<\/td>https:\/\/svn.example.com\/repos\/myproject<\/td>TLS and web-integrated auth<\/td>Requires Apache-based SVN setup, not covered here<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    Import code and run basic SVN operations<\/h2>\n\n\n\n
    Import your existing source once, then have users work from checked-out working copies.<\/p>\n\n\n
    # Initial import from server or a machine with repository access<\/span>\nsvn import \/path\/to\/source file:\/\/\/srv\/svn\/myproject -m \"Initial import\"<\/span>\n\n# Developer workflow<\/span>\nsvn checkout svn:\/\/SVN_SERVER_IP\/myproject myproject<\/span>\ncd myproject\nsvn status\nsvn add newfile.txt\nsvn commit -m \"Add new file\"<\/span>\nsvn update<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    Common pitfalls and best practices<\/h2>\n\n\n\n
    • Avoid anonymous write access<\/strong> unless you explicitly want an open repository.<\/li>
    • Keep one clear repository layout<\/strong> to avoid mixing repository root and project subfolders.<\/li>
    • Use strong passwords<\/strong> and rotate them periodically.<\/li>
    • Back up repository data<\/strong> (especially db<\/code>) on a scheduled basis.<\/li>
    • Prefer service management<\/strong> (systemd\/init) for production daemon startup instead of ad-hoc shell sessions.<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"
      This step-by-step guide shows how to set up an SVN server with svnserve, create a repository, configure authentication, and connect clients. It also covers secure defaults and core import\/checkout\/commit commands.<\/p>\n","protected":false},"author":1,"featured_media":3579,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[2],"tags":[],"class_list":["post-380","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorised"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/380","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=380"}],"version-history":[{"count":2,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/380\/revisions"}],"predecessor-version":[{"id":79260,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/380\/revisions\/79260"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media\/3579"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=380"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=380"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=380"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}