cloudplow VS gluetun

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.

healthcheck: # https://github.com/qdm12/gluetun/issues/641#issuecomment-933856220 test: "curl -sf https://example.com || exit 1" interval: 1m timeout: 10s retries: 2

I have containers a,b,c. Container C is running Gluetun (https://github.com/qdm12/gluetun) which is a VPN container.

The last couple of years I have been donating to Gluetun.

One option I could find is Gluetun, which looks very popular and actively maintained. In this case we have one single point of contact with VPN provider. The other containers should be run with network_mode: service:gluetun. If I understand correctly, those container will use VPN for every network operation, even for inter-container communication. Would they be visible for the containers not attached to gluetun (e.g. the SWAG reverse proxy)?

Try setting it up. https://github.com/qdm12/gluetun See if it works for your needs.

After some digging around, I found this project, which I think should get a lot more light on itself. It allows to setup port-forwarding on linux very easily, together with a lot of other things !

I setup Gluetun with qbittorrent in docker. Gluetun connects to the nord via manual login and I get to choose the specific servers I want it to you in its environment variables.

Hi guys, I have a dumb question: according to their github page, one of the features is the killswitch. It is not clear to me whether this would shutdown other containers (connected to it) when vpn drops, or only when the whole internet connection goes down

# See https://github.com/qdm12/gluetun/wiki