Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
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
http://prereading.pgblitz.com | Discord ( !prereading )Reference Shortcut -
Table of Contents
- Word of Caution
- Defining the Mission Statement
- Scope Development
- Basic Key Workings
- Primary PlexGuide Programs
- Resource Development
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
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.
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
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