svnsync does replay the commits, but puts a remote dependency into the commit process, which I would like to avoid.
Here is what I am considering for my situation with a separate svn and trac servers. On the svn server, have a post commit hook which stores the commit info in a file in a spool directory. Run a cron script on the svn server every 5 minutes which rsyncs the svn repo to the trac server, scans the commit spool directory, for each commit uses ssh to run the trac post commit script on the trac server, then deletes the commit file. Eventually I could have simple daemon process scan the spool directory and does the same process in near real time. Any reason why this would be a problem for trac? Ben On Wed, Mar 5, 2008 at 10:48 AM, Aaron D. Marasco <[EMAIL PROTECTED]> wrote: > > On Wed, Mar 5, 2008 at 1:04 PM, BenT <[EMAIL PROTECTED]> wrote: > > > > > > Is it advisable to setup trac on a box separate from the svn repo and > > simply use a cron'ed rsync script to mirror the repository to the > > server where trac is installed. Are there any drawbacks to this? I > > would prefer this system to synsync. > > For starters, you wouldn't be able to have post-commit scripts do things > like scan commit messages for references to tickets. As for svnsync - I > dunno if that replays each transaction and executes all hooks or not. > > - Aaron > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
