Would it be possible to have a read-only mode for MyTVSeries, so that it never goes online and never writes to the database? That way one instance of MyTVSeries in the house could get online updates and administer the database, and all the other instances of MyTVSeries around the house could just slave off the first instance's database.
Read only mode? (1 Viewer)
- Thread starter Dare
- Start date
- March 10, 2006
- 4,434
- 1,897
- Moderator
- #2
Proper server/client(s) support is being worked on, until then you can try unsupported measures such as: UserGuides/CentralisedDatabases - MediaPortal Manual Documentation
Check the forum otherwise, other users have written SQL sync scripts that you can use to achieve your read-only desire.
- Thread starter
- #3
Okay, I just thought putting a kill switch into the program that prevents it from downloading anything from the internet or writing anything to any databases would be a quick and easy workaround until "proper" server/client support was implemented. It isn't elegant or pretty, but this version of the code is on its way to the dustbin soon anyway, right? As soon as MP2.0 comes out. Might make life easier in the short term. I don't mind a couple extra warts for now.
I set up a share on the master machine containing the databases, and set the share permissions to read-only, because I don't want the remote clients to modify anything. I also changed the database and thumbs paths in the MediaPortalDirs.xml file as the referred document instructed. MP-TVSeries doesn't like that at all. It works, but it's sloooooooow. I searched around the forum for other ideas, but I really didn't find anything. I'd appreciate any suggestions.
I set up a share on the master machine containing the databases, and set the share permissions to read-only, because I don't want the remote clients to modify anything. I also changed the database and thumbs paths in the MediaPortalDirs.xml file as the referred document instructed. MP-TVSeries doesn't like that at all. It works, but it's sloooooooow. I searched around the forum for other ideas, but I really didn't find anything. I'd appreciate any suggestions.
- August 20, 2007
- 2,159
- 750
- Moderator
- #4
AW: Read only mode?
Disabling write access to the DBs for todays imple,mentation is not a good idea, as you realized yourselve.
I think the best solution today would be to use some sort of sync tool and a standbyhandler to achive, that the local data is going to be synced with your masterdata. You would have to close and restart MePo for this to male sure, the DBs are not locked - thumbs and XMLs ahould be no problem.
A solution with a centralized DB with userprofiles and separation of the functoonalities for client/display side and update processes for sure is the way I am also looking forward, but I assume it won't come quickly, because it requires lot's of work ...
Disabling write access to the DBs for todays imple,mentation is not a good idea, as you realized yourselve.
I think the best solution today would be to use some sort of sync tool and a standbyhandler to achive, that the local data is going to be synced with your masterdata. You would have to close and restart MePo for this to male sure, the DBs are not locked - thumbs and XMLs ahould be no problem.
A solution with a centralized DB with userprofiles and separation of the functoonalities for client/display side and update processes for sure is the way I am also looking forward, but I assume it won't come quickly, because it requires lot's of work ...