autoscan VS DietPi

Use Cloudbox/autoscan instead. Plex Autoscan is not maintained anymore, you can see the repository is archived.

If you use *arr to manage your downloads try setting up the "Connect" section of it with Plex and only scanning when you import/add new media to save on the periodic scans for no reason, or perhaps check out https://github.com/cloudbox/autoscan as I've heard good things about this as well.

You should now use this instead: https://github.com/Cloudbox/autoscan

This tool is designed to let sonarr/radarr directly communicate with tdarr, much like autoscan is able to communicate between sonarr/radarr and plex/emby/jellyfin.

The solution to have plex refresh the metadata after a bazarr subtitle add is to use autoscan. NOT plex_autoscan, but autoscan. This is the newer version. You also need autoscan-adapter, the critical piece of the puzzle. Autoscan by itself lets bazarr/sonarr/etc notify plex to update libraries. The autoscan-adapter helps autoscan be able to actually refresh plex metadata so the new subtitles from bazarr can be found. This is all actually very easy to implement using docker-compose. Refer to the docker-compose setup in the autoscan-adapter github.

I recommand using Autoscan. If you're using the *arr stack to download your medias, it can then automatically trigger a scan. The *arr stack can do this without autoscan for jellyfin, but the advantage of autoscan is that you can plug it to any of your other means of downloading medias by just calling its webhook

DietPi is a lightweight Debian based Linux distribution for SBCs and server systems, with the option to install desktop environments, too. It ships as minimal image but allows to install complete and ready-to-use software stacks with a set of console based shell dialogs and scripts.

The source code is hosted on GitHub: https://github.com/MichaIng/DietPi

That's a good point, but the array of devices supported by the DietPi team is extensive: https://dietpi.com/

Before someone starts the usual yadda yadda about the RPi biger community, the OS not having long time support etc. I would repeat one more time: do not rely on board vendor supplied images; this is valid for pretty much all boards. Just go to Armbian or DietPi pages and you'll almost certainly find one or more images that work on your board and forums to discuss about them with very knowledgeable people.

https://www.armbian.com/download/

https://dietpi.com/#download

Those projects are well worth a contribution, as they don't have a giant like Broadcom behind them.

> bananapi do a lot of boards but their software story has been a bit poor

This is quite common with other board manufacturers too. I'd rather suggest to ignore completely their cobbled together distros, often also tainted by proprietary modifications, that become unmaintained in a few years, and see if they're among the many supported by Armbian or DietPi.

https://www.armbian.com/download/

https://dietpi.com/#download

The full release notes can be found at: https://dietpi.com/docs/releases/v8_25/

RPi OS = diet pi https://dietpi.com/ - initial config via text file - SDcard burning out partially mitigated as writes log files to ram then flushes to SDcard reducing write cycles

You could also try very minimalistic distros like TwisterUI or DietPi which are most known for their use in the RasprebbyPi / SBC computers but which also have editions for desktop / laptop.