cloudplow VS DietPi

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.

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.