It's a Java process that runs alongside Apache and MOD_DAV_SVN to make a
full Merkle tree of the repo. Implicitly too, any sub-directory within. It
attempts to maintain different trees for people with different read
permissions/groups. Coming with it, a Docker image that sets it all up
together. Really that last is a demo, but it does place the SvnMerkleizer
within the same directory structure as the Subversion repo itself. See
within the line of code for that
While Svn keeps SHA1 for each file resource within the repo, it does not do
that for directories. Hence I made this tech.
Along the way I created a "service virtualization" tech called Servirtium
that is more interesting to enterprise Java teams than anyone else, but
some of the tests for SvnMerkleizer use Servirtium to record 15K PROPFINDS
and OPTIONS operations and allow them to be used in playback.
Pull Requests accepted.
Received on 2019-06-14 17:22:16 CEST