Pre Reading

Table of Contents

1. Intro
2. Caution
3. Defining the Mission Statement
4. Scope Development
5. Basic Key Workings
6. Primary PlexGuide Programs
7. Resource Development
8. Summary

---

1. Intro

Welcome to the pre-reading Area. Our goal here is to provide you a list of orderly information to help you in the process of understanding how the PTS fork operates.

We want to provide you a fundamental understanding of why PTS fork exists and what purpose it serves! Here are the fundamental questions on what created PTS fork.

• Is there a way to deploy a server in 30 minutes and have full-fledged programs operational?
• Is there a way to backup and recover a server quickly?
• Is there a way to avoid dependency hell that typically comes with Linux?
• Is there a way to move data to the cloud, instead of piling up endless hard drives?
• Is there a way to utilize Google Drive without reaching a read/write file transfer ban?
• Is there a way to deploy a server under numerous conditions; even move data from various configurations?
• Is there a way that we can teach others Linux along the way and assist those who aspire to learn?
• Is there a way to transfer PTS documented use to a script?
• Is there a way to easily fork and allow users to make modifications within seconds to test or utilize?
• Is there a way delegation of knowledge can be shared, rather than stuck with a few primary coders?

As you can see, there are a lot of questions and too few answers. Why? Because everyone who desires to deploy a server has a certain configuration, limited resources, and a different pool of knowledge that truly simplifies the entire process. First, we must define a scope and/or a mission.

2. Caution

Before going any further, here are some warnings to head to avoid unnecessary preliminary mistakes

• PTS will only install on Ubuntu 18 or LTS and Debian 9 (install at your own risk!)
• PTS requires x86/x64 architecture process (Intel and/or AMD)
• Do not use Raspberry Pi to run PTS
• PTS is designed for clean servers (users will have blocked ports or programs that interfere with PTS)
• PTS requires root/Sudo access

3. Defining the Mission Statement

A. Mission Statement

PTS is a fork of PGBlitz / Plexguide, an all-in-one media solution that deploys a Media Server through the use of either your local HDD or Google Drive; serving as unlimited back-end storage. PTS utilizes Ansible and Docker to streamline your Media Server while deploying multiple tools for your server operations.

B. Talking Points

In general, our mission and primary goal is to create an all-in-one media solution. To enable the mission statement, the users are required to have resources either through local hard drive or through the means of a cloud drive. It is recommended to utilize Google Drive in that it becomes another chore to move data locally to Google Drive down the road while facing Bandwidth constraints. Meanwhile, the endstate is to utilize Ansible and Docker to streamline your server operations, while using multiple tools. Hence, we must consider how to develop tools to aid us in our server quest development process.

4. Scope Development

A. General

Now that we have a mission statement, we need to define a scope. The scope should be based on our initial problem statement, combined through the use of our mission statement. The key thing to PTS's heart is that we care about the user understanding and learning something through the process. Through frustration, learning occurs ... and that is OK. PTS will never be perfect, but it gets better every day and through the support of the users. We learn together.

B. Scope

PTS requires the following scope processes:

• Develop a program that can deploy locally or remotely
• Ensure that the script is able to open and closed ports as required
• Simplify the coding process by providing the user the ability to easily modify the code
• Pave a way of understanding to the user on how the process works (that is why you are here)
• Provide the ability for a user to utilize an IP address or domain to reach the programs
• To stack containers to deploy in a quick and efficient manner
• To ensure the program is fluid within its execution
• To ensure that all users can participate in the process (as long as users respect others < key)
• Develop a process to ensure that data integrity is maintained
• Deploy mounts to enable data to transfer
• Finally, users get something out of this process through learning

By keeping a simplified scope, it becomes easier to create a vision for PTS which the process of continued understanding is further provided.

5. Basic Key Workings

In this section, we'll talk about what some of the programs are in a limited manner. Click the following links for more information

• Docker
• Ansible
• RClone
• Traefik
• PTS Editions

6. Primary PTS Programs

• PTS Shield
• PTS Clone
• PTS Box
• PTS Press

7. Resource Development

• Server Planning
• UseNet or Bittorrent
• Install
• Extra PTS Commands
• PTS Repos
• Common Issues

8. Summary

You have a long journey ahead, but feel free to visit our Discord and read through most of the wiki. Once done, you'll have a better appreciation of Linux, Virtualization, and working with a Community that learns something new together every day.

-Thanks-