Skip to content

Pre Reading

Admin9705 edited this page Mar 5, 2019 · 18 revisions
WANT TO HELP? CLICK THE ★ (STAR LOGO) in the Upper-Right!

  • 📂 [Click Here] - Google G-Suite (Unlimited Hard Drive Space & Storage)
  • 📂 [Click Here] - Top Performance NewsHost! - Blitz Members Receive a 58% Discount

Reference Shortcut - | Discord ( !prereading )

Table of Contents

  1. Intro
  2. Word of 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 PlexGuide's PreReading Area. Our goal here is to provide you a list of orderly information to help you in the process of understanding on how PlexGuide operates.

First we want to provide you a fundamental understanding on why PlexGuide exists and what purpose it serves! Here are the fundamental questions on what created PlexGuide.

  • Is there a way to deploy a server in under 30 minutes and have full fledged programs operational?
  • Is there a way to backup and recover a server in a hasty manner?
  • 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 harddrives?
  • 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 PlexGuide's 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 to 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. So what do we have to first? First, we must define a scope and/or a mission.

PG Introduction Video

2. Word of Caution

Before going any further, here are some warning to follow so you do not waste your time and our time!

  • Installs only on Ubuntu and Debian (risk on your own for other distros)
  • Requires an x86/x64 process (Intel and/or AMD)
  • Do not use Raspberry Pi
  • Designed for clean servers (users will have blocked ports or programs that interfere with PG)
  • Root/Sudo Access

3. Defining the Mission Statement

A. Mission Statement

PlexGuide is an all-in-one media solution that deploys a Media Server through the use of your Local HD or Google Drive; serving as an unlimited back-end storage. PlexGuide utilizes Ansible and Docker to streamline your Media Server, while deploying multiple tools for your Server Operations.

B. Talking Points

In general, our mission is to create an all-in-one media solution and that is the primary goal. 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 recommend to utilize Google Drive in that it becomess 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

So 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 PlexGuide's heart is that we care about the user understanding and learning something through the process. Through frustration, learning occurs ... and that is ok. PlexGuide will never be perfect, but it gets better everyday and through the support of the users; we learn together.

B. Scope

So PlexGuide 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 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 hasty and efficient manner
  • To ensure the program is fluid within it's execution
  • To ensure that all users can participate in the process (as long as users respect others < key)
  • Develop 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 PlexGuide which the process of continued understanding is further provided.

5. Basic Key Workings

Ok... we get it... enough of the philosophy (and some people do love it right). In this section, we'll talk about what some of the programs are in a limited manner. Click the following links for more information

6. Primary PlexGuide Programs

7. Resource Development

PG Install Video

8. Summary

You have a long journey ahead, but feel free to visit the forum 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 everyday.


The PG Team & Admin9705


  1. Introduction
  2. PG YouTube Channel
  3. Recommended Pre-Reading

Starter Info

  1. Server - Storage Planning
  2. Usenet or BitTorrent
  3. G-Suite Signup
  4. Recommended NewsHosts
  5. PG Editions
  6. PGBlitz Repos
  7. Common Issues

Deploy & Config

  1. SSH Server Access
  2. Create a SUDO User
  3. Install PlexGuide
  4. WatchTower
  5. Download Path

RClone Basics [Expand]
  1. Google OAuth Keys
  2. GDrive
  3. TDrive
  4. RClone Manual Deploy

Data Transport
  1. PG Clone
    1. PG Move
    2. PG Blitz
    3. 2nd HD Option

Key Components

  1. Traefik
  2. Port Guard
  3. PG Shield
  4. PG Press

PG Apps

  1. Official Apps
  2. Community Apps
  3. Custom Containers
  4. Accessing PG Apps
  5. App Port Scheme
  6. Plex to AutoScan
  7. Remote Path Mappings
Core Apps
  1. Emby
  2. Jackett
  3. Jellyfin
  4. LazyLibrarian
  5. Lidarr
  6. Netdata
  7. NZBGet
  8. Ombi
  9. Plex
  10. Portainer
  11. qBittorrent
  12. Radarr
  13. RuTorrent
  15. Sonarr
  16. Tautulli
Community Apps [Expand]
  1. AirSonic
  2. AllTube
  3. Beets
  4. Bitwarden
  5. BookSonic
  6. CaAdvisor
  7. Cloud Commander
  8. DDClient
  9. Deezloaderremix
  10. Deluge
  11. DelugeVPN
  12. Duplicati
  13. EmbyStats
  14. Gazee
  15. Handbrake
  16. Headphones
  17. Heimdall
  18. HTPCManager
  19. JDownloader2
  20. jd2-openvpn
  21. Kitana
  22. Logarr
  23. MariaDB
  24. McMyadmin
  25. MEDUSA
  26. Mellow
  27. Monitorr
  28. Muximux
  29. Mylar
  30. NextCloud
  31. NowShowing
  32. NZBThrottle
  33. Organizr
  34. pyLoad
  35. Radarr4k
  36. Resilio
  37. rflood-openvpn
  38. ShareSite
  39. Shoko Anime Server
  40. SpeedTest
  41. SyncLounge
  42. Syncthing
  43. The Lounge
  44. Transmission
  45. Trakt.or
  46. Ubooquity
  47. MakeMKV

Cloud Instances

  1. Google Cloud - GCE
    1. Automated setup
    2. Multiple NVMe Drives in raid0
  2. Hetzner Cloud

Tools & Services


UseFul Reading

  1. Scripting Area
    1. Auto Upload for Sonarr and Lidarr
    2. Auto Delete Log
    3. Plex Plugin DB Backup
    4. Plex fast BACKUP


Clone this wiki locally
You can’t perform that action at this time.