Possibly issue with new beta (and soon to be live) emby server #394
-
|
I love your watchstate and it runs daily for my own user to keep my primary emby server and my hot standby emby server in sync. Emby devs however have implemented a change on the latest .66 beta that replaces this plugin with a new 'all in' backup system - which removes the abiity to 'cherry pick' what you want to restore - it is a complete copy of the server - inc server name etc etc. This is due to go live this month for everyone I believe. I posted that this will not work for me, and they have said the move to the database for almost all of the emby stuff will meand it cant be done this way. I am just posting this here in case they also break the method you are using to sync users. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
After back and forth with the emby devs, they have agreed to provide the original emby backup plugin which has only the user restore process - so maybe no issue for watchstate functionality after all. It is posted in page1 of the above link. Note - you can only see these links if you are part of the emby beta users. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Thank you for bringing this up, Thankfully we don't use this particular functionality of emby. We use the API directly. And you could also use watch state to sync your other users as well just mount different data dir for each user and run import&export you don't have to run 25 container those users can be synced manually using cronjob. #136 (comment) |
Beta Was this translation helpful? Give feedback.
Hi,
Thank you for bringing this up, Thankfully we don't use this particular functionality of emby.
We use the API directly.
And you could also use watch state to sync your other users as well just mount different data dir for each user and run import&export you don't have to run 25 container those users can be synced manually using cronjob. #136 (comment)