Examples of using Svnsync in English and their translations into German
{-}
-
Colloquial
-
Official
-
Ecclesiastic
-
Medicine
-
Financial
-
Ecclesiastic
-
Political
-
Computer
-
Programming
-
Official/political
-
Political
Partial replication with svnsync.
Type'svnsync--version' to see the program version and RA modules.
That's repository replication via svnsync in a nutshell.
But obviously, svnsync requires both read and write access to the mirror repository.
As of version 1.4,Subversion provides a program for managing scenarios such as these- svnsync.
Let's walk through the use of svnsync in a somewhat typical mirroring scenario.
Used by svnsync copy-revprops to specify a particular revision or revision range on which to operate.
Another requirement of the target repository is that the svnsync process be allowed to modify revision properties.
Our walkthough uses svnsync, which is covered in more detail in the section called“Replication with svnsync”.
After this is done,we configure the master server's post-commit hook script to invoke svnsync on each slave server.
Description The svnsync synchronize command does all the heavy lifting of a repository mirroring operation.
This property is generally only observedwhen such an operation is active-or when an svnsync command failed to cleanly disconnect from the repository.
Causes svnsync to steal, as necessary, the lock which it uses on the mirror repository to ensure exclusive repository access.
Notice that we provided a username and password as arguments to svnsync-that was required by the pre-revprop-change hook on our mirror repository.
Warning svnsync is very sensitive to changes made in the mirror repository that weren't made as part of a mirroring operation.
Available subcommands: initialize(init) synchronize(sync) copy-revprops help(?,h)$ We talk more about replicating repositories with svnsync later in this chapter see the section called"Repository Replication.
Revision(-r) ARG Used by svnsync copy-revprops to specify a particular revision or revision range on which to operate.
We strongly recommend that you specify the source URL on the command-line, especiallywhen untrusted users have write access to the revision 0 properties which svnsync uses to coordinate its efforts.
Also, svnsync stores the source repository URL provided at mirror initialization time in a bookkeeping property on the mirror repository.
This option should only be used when a lock exists in the mirror repository and is known to be stale-that is,when you are certain that there are no other svnsync processes accessing that repository.
Svnsync help info info: usage: svnsync info DEST_URL Print information about the synchronization destination repository located at DEST_URL.
Also noteworthy is that svnsync performs careful bookkeeping that allows it to be safely interrupted and restarted without ruining the integrity of the mirrored data.
Svnsync needs to be able to set and modify revision properties on the mirror repository because those properties are part of the data it is tasked with mirroring.
Disable-locking Causes svnsync to bypass its own exclusive access mechanisms and operate on the assumption that its exclusive access to the mirror repository is being guaranteed through some other.
Svnsync A program for incrementally mirroring one repository to another over a network svnrdump A program for performing repository history dumps and loads over a network.
Because svnsync works within the framework of that repository's hook system, the default state of the repository which is to disallow revision property changes;
So svnsync follows up with an immediate series of property modifications that copy into the target repository all the revision properties found for that revision in the source repository.
That svnsync stores the source repository URL in a bookkeeping property on the mirror repository is the reason why you have to specify that URL only once, during svnsync init.
As such, svnsync has the same sorts of limitations that the repository dump stream has, and does not include such things as the hook implementations, repository or server configuration data, uncommitted transactions, or information about user locks on repository paths.
Svnsync has to follow up with an immediate series of property modifications that copy into the target repository all the original revision properties found for that revision in the source repository, which also has the effect of fixing the author and datestamp of the revision to match that of the source repository.