Zach,
It's bugged me for some time now that a lot of Trac's power isn't being
used by us because it can't access our SVN repo. But we still want to keep
using Sourceforge and Trac doesn't yet support remote SVN repositories. Is
there any chance you could look into one of the workarounds?
There's an alpha attempt at letting you use remote repositories at:
http://www.meadowy.org/~gotoh/projects/remote-svn-plugin/wiki - But that
doesn't look ready according to the author.
The Trac ticket for enabling this feature seems to have some workarounds
posted in comments: http://trac.edgewall.org/ticket/493
The easiest appears to be:
"Among the possible workarounds, there's also svnsync, which is a new tool
part of Subversion 1.4. It allows to easily replicate repositories, from URL
/ to URL, which gives you a great deal of flexibility.
For example, you can set up a post-commit hook on the central repository
that will trigger the replication to a slave repository on the server where
you run Trac. Alternatively, on that Trac host, you can periodically call
svnsync which will pull new revisions from the central repository.
I've tested that tool with 1.4.0rc5, and it works fine. Of course you could
have done the above using svk mirror, but svnsync is more straightforward to
install and use."
SF.net doesn't have any post-commit hooks to replicate, but we could try to
use svnsync and pull from it to our Trac box, correct?
Thanks,
Chris
--
http://cwilliams.textdriven.com
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Rubyeclipse-development mailing list
Rubyeclipse-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
