PTS Editions - n05urpr1532-MHA-Team/PTS-Team GitHub Wiki

Table of Contents

  1. Intro
  2. PTS YouTube - Editions
  3. GDrive Edition
  4. GCE Edition
  5. Local Edition - Solo Drive
  6. Local Edition - Multiple Drives
  7. Summary

1. Intro

PTS offers a multiple array of options in order to deploy. From running on a dedicated server, vps, virtual machine, or cloud instance; you can store your data via a local edition (with multiple HD support) or through google drive.

Finally, you can take advantage of our Google Cloud Edition (GCE Feeder) where we assist in setting up and deploy your Google Cloud Instance automatically! PTS has been designed for ease of use and maximum flexibility!


2. PTS YouTube - Editions

Watch this video first before selecting a type! Failing to do so will result in lots of work in shifting in accordance with your future desired requirements!

PTS Edition Video


3. GDrive Edition

A. Usage

  • Most Commonly Used
  • Utilize Google GSuite for truly unlimited space

Highlighted Selections are the GDrive Editions

Basic Information

The GDrive Edition will display as such. You'll notice the type of edition that is selected and that (1) has the transport data menu; which is basically for your rclone and gdrive mounts! The GDrive Edition will most likely suit your needs due to lower costs (if you store tons of data). Remember, GSuite has a 14-day trial, so this will give you enough time to explore this option!


4. GCE Edition

A. Information

The GCE Feeder Edition is the same exact thing as the GDrive Edition, except that it utilizes a Google Virtual Machine Instance. If you paid attention, you may have noticed that Google gives offers you a $300 credit on their Google Cloud Console. Long story short, this edition deploy on their instance and sets everything up for you; including mounting the NVME drive that is associated with the instance. There are two ways of going about this; the difficult way and the easy way.

B. Automated Deployment

REQUIRED: Sign Up First for Business GSuite First - Click Here

  • Effort: Easy
  • Note: Must have PlexGuide running on a box already
  • Super Easy Deployment through an interface (very light work required)
  • Deploys the Virtual Machine (Instance), Firewall, and IP Address

Video is dated, but will provide general information


5. Local Edition - Solo Drive

A. Intro

  • For Rare or Light Plex Usage
  • DOES NOT Utilize Google GSuite. Just the Drive the Data is On!

Does NOT Utilize Google Drive; just local HD’s!

B. Information

Using a solo drive (built-in) is dead simple to utilize. Below is a picture in which you will deploy it and exit! That’s it!

Does NOT Utilize Google Drive; just the standard built in HD!


6. Local Edition - Multiple Drives

A. Introduction

  • For Medium Plex Usage
  • DOES NOT Utilize Google GSuite. Just the Drive the Data is On!

Does NOT Utilize Google Drive; just local HD’s!

B. Information

The use of multiple hds will display information in the two screenshots as such. When deploying the multiple HD's, IT DOES NOT utilize the current disk that your OS is installed. You may add it, but it is a bad idea. For example, if you have two additional drives; mergerfs will run the diskspace down on one drive until it reaches 10GB and then will start to fill the next disk! If you added your OS disk, MergerFS will fill your OS disk drive (which is bad) and with no space, it your system will crash. This setup requires that user understands some basics about the use of multiple disk and linux formatting usage. If you have questions, please visit us on the forums!

Does NOT Utilize Google Drive; just the standard built in HDs!

Next, you must setup your mountpoints or your HDs. You are responsible to mount your drives and have linux recognize it in the first place. We are unable to automate this portion. Please see the video for more information. If making any changes, please REDEPLOY mounts afterwards for the changes to take affect!

Ensure the mountpoint or drive exists!


7. Summary

Keep in mind that selecting the right edition from the start with proper planning makes life easier. You can always switch between the editions, but you will be responsible to migrate data as you see fit.


⚠️ **GitHub.com Fallback** ⚠️