cloudplow VS autoscan

I might just stick to my previous idea, but it's not user friendly for other people in my household. I'm using Cloudplow. So I'll add an rclone_extras tag for '--exclude-from' that references an excluded list.

Multiple in parallel. To avoid this, you could write a simple bash script to only allow one instance of itself. Example here. Alternatively, I recommend checking out cloudplow.

Something else of interest might be Cloudplow or Crop. Cloudplow is a Python implementation of rclone that extends it to a serviceable state for automatic transfer of files. Crop does this similarly but uses the go language.

Check out Cloudplow and rclone.

You can use something like cloudplow to get around the 750gb limit. Cloudplow can automate using different service accounts which each have their own limit.

As you’ve mentioned you’d like to use rclone, I’d suggest you read up on unionfs or mergerfs and configuring something like CloudPlow or Crop to manage uploads to the cloud for you.

As you have a linux seedbox, I would look into cloudplow.

One way to accomplish this, at least in function, would be to not use the mount to upload. Use something like mergerfs to combine the mount folder and a local folder. Stuff gets written to to the local folder while stuff gets read from both. Then on a schedule use a script to automatically upload stuff. cloudplow is also an option instead of just calling rclone directly to upload. Instead of operating on a fixed schedule it watches the local folder's size and uploads when needed. This helps you not run out of space.

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