PTS Clone

Table of Contents

1. Intro
   1. Background Information
   2. Key Authentication Warning
2. Transport System
   1. Methods
   2. Additional Considerations
3. Summary

---

1. Intro

Welcome to PTS Clone! PTS Clone is a suite of services that utilize RClone with a specialized custom configuration file to enable fast, hasty, and more simplified deployment through PlexGuide's deployment interface.

i. Background Information

We discovered over time that editing RClone through the use of RClone config is both a simple and complex process depending on the user's requirements. The PTS team has cleaned up the config and only left directly what is required for PTS to operate. RClone can be quite overwhelming because it covers both a broad scope of services that do a great job by attempting to unify both simplicity and flexibility; both within its large scope of deploying cloud drives. By understanding how RClone operates, we are able to create PTS Clone; while providing personnel Google's Authentication for your project!

ii. Key Authentication Warning

Do NOT ever trust anyone who runs a project that provides OAuth from their servers. PTS is dedicated 100% to providing you your own privacy and access. Others will have access to your data and more if you provide them your keys or authenticate through their services!

2. Transport Mode

When utilizing PlexGuide the first time and selecting PTS Clone, the user must select a transport mode. Transport modes are explained in detail below.

i. Modes

There are four transport modes for the user to chose from. They are the following:

• PTS Move /w No Encryption
• PTS Move /w Encryption
• PTS Blitz /w No Encryption
• PTS Blitz /w Encryption

ii. Additional Considerations

Before selecting a method, consider the requirements. The process can be simple or quite complex based on what is required. Be warned that switching from unencrypted to encrypted or vise versa will require the user to download all of their data and then re-upload. Doing so also creates double bandwidth considerations (upload and download of the same data). Personally, I utilize the unencrypted versions which allows you to see all of your data through Google Drive.

2. Summary

/mnt/unionfs is a union of /mnt/downloads, /mnt/move, /mnt/gdrive, /mnt/tdrive. It also has /mnt/tcrypt and /mnt/gcrypt if using encryption. Processing location default /mnt

Note: we will use /mnt here for ease of explaining but replace /mnt with your processing location.

How it works with 8.3 and above: Files download to:

/mnt/incomplete/nzb
/mnt/incomplete/torrent

etc

Once completed, your downloader moves them to:

/mnt/downloads/nzb
/mnt/downloads/torrent

etc

Once your download is completed sonarr/radarr/lazylibrarian/lidarr will be notified. They then rename the file and move it to your library. Radarr and Sonarr have download mappings (you need to configure them). It will replace the path the downloaders give,

/mnt/downloads/nzb/ to
/mnt/unionfs/nzb/

Sonarr/radarr/etc will then organize and rename the files and import them into the library, which is /mnt/unionfs/category/[...]

The real location of the files is /mnt/downloads/nzb or torrent/[...].

The files are now ready for upload. Blitz/Move script runs and moves any completed files to /mnt/move, ignoring any files underneath a downloader folder (/mnt/downloads/nzb). It will move things like /mnt/downloads/tv, /mnt/downloads/abooks, /mnt/downloads/mycustomcategory, etc).

So at this point, your files are in /mnt/move, ready to upload.

Now that uploads are finished it will delete empty folders underneath /mnt/move/category and /mnt/downloads/category/

Notes:

• The process from going to completed to upload is a lot faster now, you may miss it.
• You should connect sonarr/radarr to plex and make sure you setup mappings (see their wiki pages for configuration)
• Move/Blitz will not process downloads while there is an active upload. Think of batches, it grabs whats ready, process and upload, then repeat.