On 25 October 2014 22:49, Lorne Tyndale <[email protected]> wrote:
> (unless of course, you specifically tell it to use a database called
> Rivendell, but that would not be wise)
>
But even then, it is very unlikely that the two apps will have tables with
name conflicts.
Overall, it is mostly a question of performance.
The database is on the same machine as the actual playout (rdairplay):
Are you doing your accounting on the playout machine?
Yes: Please dedicate another machine for this task. If there is no
way around this, then create a new database for your
billing purposes.
No: Install MySQL on the machine on which you are doing the billing.
The database system is on a separate machine:
Create a new database for billing. Make sure you allocate enough
resources so that
concurrent use will not slow down the Rivendell database. Overall, this
kind of setup
is very common, nothing in particular should happen (e.g. corruption).
Consider moving the Rivendell database back to the playout machine.
If budget is tight, consider alternatives like setting up a Raspberry Pi
with an external USB drive (total about $100). It could make a decent
database server, ideal for low performance tasks, that you can hide
anywhere convenient. Don't put the Rivendell database on it, though.
--
Sébastien Leblanc
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
