@simon_lefisch said:
If possible, do you have a write up I can follow? I’ve looked at the tutorial on the plexdrive github but I’m either not understanding correctly or it does not enough info for me to follow (most likely the former). Thanks for any help you can provide.
Here’s a quick summary:
Rclone - mounts, copies, syncs between any combination of Google, OneDrive, DropBox, local file storage, and a number of other services. Also has encrypting capabilities built in so files can be encrypted/decrypted on the fly when mounting/copying/syncing. Lot’s of different settings that come into play for the various methods being used and this allows you to tweak it for your environment, bandwidth and preferred thresholds.
PlexDrive - mounts Google drive locally with pre-canned settings designed to optimize the Plex experience. Has some key parameters that can be tweaked for your environment and to minimize the amount of actual API hits (i.e. file scanning) that occur within Google. Originally built to overcome the frequent bans received by using Rclone and scanning (especially first time) huge libraries.
PlexDrive really does one thing and does it really well: mounts Google for Plex playback, typically on a VPS (but could also be used locally where the Plex server and Plex viewer are on the same network). Its main benefit is that it caches the metadata from Google so, once that’s stored in its local database/cache, a “refresh” of your Plex library happens nearly as fast (or in some cases, faster) than it ever did on a local server, let alone Plex Cloud or Rclone-mounted Google on a VPS.
If you want to copy large amounts of data from location A to location B, you’ll need to use Rclone. If you want to mount something that isn’t Google, you’ll need Rclone. If you want your data encrypted, then you’ll need Rclone.
And that last statement is where you’re probably getting confused. Many people like me have a Google drive that we encrypted and mounted with Rclone. So, switching to PlexDrive means we have to decrypt everything and re-upload it, right? Wrong! Since Rclone can mount (or in this case, remount) a local directory as another drive, we simply use this process:
- Mount Google via PlexDrive to /mnt/AAA
- Remount /mnt/AAA using Rclone and its decrypter to /mnt/BBB
- Point Plex to look for its videos under /mnt/BBB/TV and /mnt/BBB/Movies
Step one gives you all the benefits of a buffering mount with the file system pointers stored locally. Step two decrypts it so that you can actually use that data. Step 3 is, well, essential since you have to point Plex somewhere! Note that Rclone is acting locally-only. It never talks to Google.
Likewise, to copy new files up to Google, you use the Rclone command (either Rclone sync or Rclone copy) along with the encrypted configuration. This means that your Rclone config file has at least two configurations in it. One to talk directly to Google in encrypted format and the other to talk to the local file system for remounting the PlexDrive directory.
If you’re not using encryption, then step 2 is eliminated and replace BBB with AAA is step 3. You’ll still use Rclone to copy files up to Google, however.