Contents
Front-end to svnsyncing a remote svn repo
Description
Note: Plugin seems to be incompatible with Trac v1.0.
Trac does not provide an out-of-the-box solution for svn repositories that don't reside on the same server as Trac. SvnsyncPlugin provides a front-end to aid in the creation of a svnsync-ed repository locally. This requires svn 1.4 to be installed locally, including the svnsync command on the $PATH.
This plugin is still a beta and is not as automated as it could be. Also, svnsync is not 100% reliable: for instance, it does not work as expected on edgewall's repositories.
Bugs/Feature Requests
Existing bugs and feature requests for SvnsyncPlugin are here.
If you have any issues, create a new ticket.
defect |
5 / 9 |
||
---|---|---|---|
enhancement |
1 / 3 |
Download
Download the zipped source from here.
Source
You can check out SvnsyncPlugin from here using Subversion, or browse the source with Trac.
Installation
General instructions on installing Trac plugins can be found on the TracPlugins page.
Svnsync, and therefore the SvnsyncPlugin, requires the remote version svn server to be at least version 1.4; see the svnsync
section of the subversion 1.4.
Configuration
To use this plugin, you must make some changes to the trac.ini
file of your Trac project. First, enable the plugin:
[components] svnsyncplugin.* = enabled
Make sure your repository type is set to svnsync
:
[trac] repository_dir = /path/to/directory repository_type = svnsync
Note that repository_dir
is used as the destination directory for the sync. You must also give the repository_url you wish to sync to:
[svn] repository_url = http://yoursvnserver.org/svn
The repository will be synced on each request. The first sync (to get all past versions) will take some time. You can get around this by using the svnsync.py script (UNIX syntax shown):
`python -c 'import svnsyncplugin, os; print os.path.dirname(svnsyncplugin.__file__)'`/svnsync.py --directory /path/to/directory --repository http://yoursvnserver.org/svn
Recent Changes
Author/Contributors
Originally developed at The Open Planning Project
Author: k0s
Maintainer: Christof Hanke
Contributors: