plex-sync VS locize-cli

For a while I used plex-sync (https://github.com/jacobwgillespie/plex-sync) to synchronize my different user’s watch statuses from my Mac and Synology, including the main admin account and managed user, but now I don’t want to use the Managed User anymore (esp since the new Discovery feature doesn’t work with Managed Users). Previously I enabled the PMS token in logs so I could use tokens to sync accounts (I could find tokens for the Home and Managed user separately) using the plex-sync script, but I see you can no longer enable tokens in the logs. My tokens have changed since I reinstalled on a new M1 Macbook Pro. I can find the main user’s token using the view XML from a library item’s Get Info but I can’t get the token for a Managed User this way.

plex-sync

Yes there is a docker container that will sync Plex watched items history between the two Plex servers. https://github.com/jacobwgillespie/plex-sync

I'm trying to run this: plex sync

Now let's install the locize-cli:

Just use this cli to synchronize the translations with your code. To see how this could look like check out Step 1 in this tutorial.

install the locize-cli (npm i locize-cli)

You can, for example, run an npm script script (or similar), which will use the cli to download the translations from locize into the appropriate folder next-i18next is looking in to (i.e. ./public/locales). This way the translations are bundled in your app and you will not generate any CDN downloads during runtime.

First you need to signup at locize and login. Then create a new project in locize and add your translations. You can add your translations either by importing the individual json files or via API or by using the CLI.

First in locize, create a dedicated version for production. Do not enable auto publish for that version but publish manually or via API or via CLI. Lastly, enable Cache-Control max-age​ for that production version.