On Jun 30, 2008, at 10:11 AM, Axel Gembe wrote: > > Noah Kantrowitz wrote: >> No, there are things we do not store in the DB. The major issues are >> attachments, config data, and VC data. While I suppose you could put >> all of those (really the whole Trac env folder) on a network file >> system, this still isn't true replication. I don't know of any good >> filesystem replication systems that don't cost $$$$$. >> > Subversion already has svnsync + webdav proxy, and replicating > repositories it is out of the scope of Trac anyways. > You're right about the configuration and attachments though. I > currently > use git to synchronize them, but thats a bad hack.
Given that model, you are just as well off by taking a pg_dump backup when you initiate the other syncs and reloading it on the backup DB. DB replication like this only makes sense when you need up-to-the- second failover and redundancy. Given that this really isn't possible with Trac, I return to my original comment of "-1". It would be nice to eventually support things like real replication and caching in Trac, but it is a good ways off. --Noah --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
