On 13/01/2012 00:12, Rob Landry wrote: > > On Thu, 12 Jan 2012, James Harrison wrote: > >> Aside from that - why not just do replication? Have your transmitter >> sites be read-only MySQL clones of the studio. > That won't work because not all the files going to each site come from the > studio. Voice tracks, for instance, get imported from a radio network on > Cape Cod, and news and weathercasts may be sent from an employee's home. Ah, that does make it more complicated. You'd really have to be looking at something quite complex in MySQL Proxy, but a more manual approach is likely to be best... >> In principle I think your way would work, though I'd probably have the >> script keep its own DB away from the Rivendell DB for simplicity's sake >> and to stop it being an issue when doing DB upgrades. > That's what I have in mind; Rivendell_sync will be a different database > from Rivendell. Yup yup - I'd also consider keeping track of a fast computable hash on the files, MD5/SHA1 or similar, so you can tell when a file on disk has changed without the DB changing, just in case. > > > Rob > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
_______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
