In general this model is unhelpful for webapps, so to the best of my knowledge it has not been explored. You could use a mix of DB replication and rsync, but I don't know of any DBs that have provisions for multi-site replication and merging.
--Noah On Sep 6, 2006, at 10:08 PM, glenn wrote: > > hi all > I've become so dependent on track - that great chunks of my day are > spent entering/modifyying tickets and adding to wiki. > > Prob is theres lots of administrative and 'thinking' I prefer to > do on > laptop on train or in cafe etc... so Im wondering if anyone has come > up with an elegant way of 'backing' up trac, then resysnchronising it > later? some sites im only contributor and so is less difficult, > others, > offline changes would need to be integrated. > > for my purposes browsing source off line wouldnt be so critical - > should I just be looking into a database replicatoin solution for my > given backend? or is there other considerations? > > thanks > Glenn > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
