[mythtv-users] Testing latest Mythv

[George Nassas]

On Jan 11, 2016, at 4:28 AM, Bjoern Voigt <bjoernv at arcor.de> wrote:

> Is there a solution which is more elegant than renaming or symlinking the mysql.txt and config.txt files?


Besides Stuart’s excellent write-up you might consider building and running myth in a virtual machine. I do this whenever I want to try something that involves DB changes. I agree with copying mythconverg into a second database instance or schema or whatever they call it and do it on your main machine, mysql in a VM is awful. Myth BE and FE in a virtual machine is fine. In my case I have an HDHR so I can test recording remotely from a VM on my Mac but you could also set up one of the network recorders like those that take HLS feeds.

The other thing to watch out for is your test system quietly expiring recordings behind your production BE's back. I had a script for copying mythconverg that also did some post-processing where the expiry interval was set to 0 which meant don’t delete except under user control. You could also set it to some high interval like two years so testing myth will never touch anything in the “Deleted” group. Maybe that has already been mentioned but this thread is getting unwieldy and I might have missed it.

- George