Choosing Between svnserve and Apache HTTPD for Subversion Access
Decide whether to use the lightweight svnserve daemon or Apache HTTPD with mod_dav_svn for your Subversion server, based on network, auth, and feature needs.
Loading…
ReadMeFeed / Community knowledge
#svnserve
Real questions. Useful conversations. Find the people who know your stack.
apache
subversionmod_dav_svn Apache connection pool vs svnserve Berkeley DB locks for burst concurrency
A deployment subject to intermittent bursts of Subversion client requests must choose between two documented server approaches for handling concurrency. mod_dav_svn relies on Apache's built-in connection pool, where acceptance is governed by server-wide client and timeout settings. svnserve with a Berkeley DB backend relies on DB_ENV lock tables and cache si
svnserve+SSH minimal footprint vs mod_dav_svn per-path authorization for constrained Subversion deployment
Design choice for a Subversion server under a resource-constrained host with a requirement for path-level access control. svnserve with SSH provides a minimal footprint and no external web server, but documented behavior shows it lacks per-path authorization. mod_dav_svn via Apache provides fine-grained access control through standard Apache directives, at t
SVN Server vs SVN Client: Resolving Concurrent Commit Latency under FSFS
SVN Server vs SVN Client: Concurrent Commit Latency The goal is to understand how Subversion’s FSFS repository handles multiple simultaneous commit requests while a client performs concurrent read operations. The repository uses a single global write lock, which may serialize commits and cause latency spikes. The behavior differs between the svnserve daemon