Differences

This shows you the differences between two versions of the page.

--- start [2026/01/02 20:12] – privacyl0st
+++ start [2026/06/17 14:57] (current) – privacyl0st
@@ Line 1: / Line 1: @@
-{{htmlmetatags>
+====== TRaSH Panda Guides: Building a Fully Automated Home Media Ecosystem ======
-metatag-description=(Complete Plex automation guide using Sonarr, Radarr, Prowlarr, Jackett, Overseerr, Unmanic, and NVENC-enabled NVIDIA GPUs)
-metatag-robots=(index,follow)
-metatag-og:title=(Plex Automation and NVENC Hardware Transcoding Guide – Trash Panda Wiki)
-metatag-og:description=(Step-by-step Plex automation and NVENC encoding guide)
-}}
-===== Welcome to Trash Panda Guides =====
-Before getting into any configuration or architecture guides, it’s important to acknowledge [[https://trash-guides.info/|TRaSH Guides]]. Without the incredible work they’ve done, nothing here would exist. A large amount of the tuning and philosophy you’ll find throughout this wiki is rooted directly in their work.
-Where this effort diverges is intent.
+Welcome to the **TRaSH Panda Guides**—the definitive implementation blueprint for designing, securing, and deploying an enterprise-grade home media ecosystem.
-TRaSH Guides are exceptional if your goal is an //**archive‑quality media collection**// — pristine releases, maximal fidelity, and little compromise. What I found after following those guides, though, is that unless you’re a hardcore cinephile with deep pockets, vast storage, and serious hardware, that approach may not align with how you actually consume media.
+While the legendary TRaSH Guides taught the community how to perfectly tune applications for the highest quality media, the TRaSH Panda takes a step back to engineer the forest they live in. This guide isn't just about configuring the ARR stack; it is about building the decoupled, multi-VLAN infrastructure that securely houses it.
-That gap is where **Trash Panda Guides** was born.
+**Disclaimer:** //This document is strictly an infrastructure guide intended for educational, technical, and academic purposes. It does not provide links, access points, indexing details, or instructions for obtaining copyrighted content.//
+===== The Monolithic Problem vs. The Decoupled Architecture =====
+Most conventional home media deployments are essentially digital dumpsters—fragile, monolithic architectures running on a single, overburdened server with dangerously permissive directory permissions (chmod 777). While a raccoon might love a messy dumpster, this centralized approach creates a massive single point of failure and represents a significant cybersecurity vulnerability.
-===== Why “Trash Panda”? =====
+The TRaSH Panda blueprint introduces a fundamentally different approach: a **decoupled, secure, and self-sustaining media architecture**. It cleans up the chaos by segregating operations into four strictly isolated functional pillars:
-Like your friendly neighborhood trash panda, we dug through the TRaSH. We pulled out what we needed, kept what made sense, and ignored what didn’t serve //our// goals. Now we’re sharing the spoils of those dumpster dives with you.
+  * **The Vault (Storage):** A hardened Network Attached Storage (NAS) layer isolated on a dedicated, non-routable storage area network.
+  * **The Brains (Acquisition):** Automated content aggregation via the ARR suite, firewalled from public-facing exposure and routed over a strict VPN kill-switch.
+  * **The Brawn (Processing):** Distributed transcoding and media optimization automated via Unmanic to ensure maximum compatibility and storage efficiency.
+  * **The Guard (Delivery & Security):** High-availability local and remote media streaming via Plex Media Server, sandboxed within a secure Demilitarized Zone (DMZ), shielded by a dedicated Edge Proxy.
-===== What These Guides Are (and Are Not) =====
+===== Master Ecosystem Architecture Topology =====
-These guides target the **Plex administrator who wants a true set‑it‑and‑forget environment**, built around consumer‑quality media.
-That does not mean poor quality.
+<mermaid>
+graph TD
-It means striking a deliberate balance:
+    PublicInternet((Public Internet)) -->|Port 80/443| EdgeProxy[NGINX Edge Reverse Proxy<br>Raspberry Pi 5]
-    ✘ Not archive‑grade remuxes that devour disk space
-    ✘ Not low‑effort junk releases
+    subgraph VLAN 20: Hardened DMZ 10.0.20.0/24
+        EdgeProxy --> MediaRequest[Media Request Server VM-B<br>Overseerr]
-    ✔ Efficient 1080p and 4K content that looks great
+        EdgeProxy --> PlexEngine[PLEX Media Server<br>Bare-Metal Engine]
+        Unmanic[Unmanic Optimization Engine<br>NVIDIA RTX 3050 GPU] -.-> PlexEngine
-    ✔ Libraries that scale without petabytes of storage
+    end
-    ✔ Systems that don’t require enterprise GPUs to function
-The configurations here //**will not**// produce junk libraries, and they //**will not**// produce an archive‑quality collection either.
-What they //will// produce is maximum efficiency.
-If you want quality content without needing petabytes of storage or an NVIDIA Quadro, you’re in the right place.
+    MediaRequest ==>|Stateful Pinhole TCP 7878/8989/8686| Firewall{Firewall Access Control Barrier<br>Default Deny Posture}
+    PlexEngine -->|Reads| Firewall
-Within this wiki you’ll find:
+    subgraph VLAN 10: Trusted Management LAN 192.168.10.0/24
+        Firewall ==> Acquisition[Media Acquisition Server VM-A<br>Prowlarr, Sonarr, Radarr, Lidarr]
+        Firewall --> Veeam[Disaster Recovery Host VM-C<br>Veeam Backup]
+    end
-  * Architectural guidance to build a secure, accessible Plex ecosystem
+    Acquisition ==>|NFS Write Path| StorageFabric
+    Firewall -->|NFS Read/Transcode Path| StorageFabric
-  * Configuration guides that allow the system to largely run itself
-  * Practical tuning rooted in real‑world performance, not theoretical perfection
-Covered services include (but are not limited to):
+    subgraph VLAN 50: Isolated Storage Network 10.0.50.0/24
+        StorageFabric[(Synology 4-Bay NAS Array<br>Unified Root Mount: /volume1/data)]
+    end
+</mermaid>
-  * Plex
+===== The Vision: Resourceful & Pragmatic =====
+Raccoons are the ultimate pragmatists, and this architecture reflects that trait. While elite enthusiast blueprints often mandate massive storage arrays and gigabit fiber for uncompressed 4K HDR Blu-ray remuxes, the TRaSH Panda architecture is a highly capable, resourceful alternative designed to maximize the hardware you actually have:
-  * Prowlarr
-  * Sonarr
-  * Radarr
-  * Overseerr
-  * qBittorrent
-  * Unmanic
-  * Jackett
-  * FlareSolverr
-  * NGINX
-You will also find guidance on hardware, networking, and security configuration to support them.
+  * **Public Trackers vs. Private Trackers:** Optimized for public trackers, leveraging aggressive automated cleanup tools ([[services:maintenance_engines|Cleanuparr]]) and strict parsing to mitigate malware risks.
+  * **1080p Cap vs. 4K Remuxes:** Capping acquisition at high-quality 1080p/720p profiles prevents storage exhaustion and network saturation.
+  * **Automated GPU Transcoding:** Uses hardware-accelerated GPU compute ([[services:unmanic|Unmanic]]) to dynamically transcode bloated legacy H.264 files into space-saving H.265 (HEVC) formats.
+**Next Step:** Proceed to the [[architecture:deployment_sequence|Deployment Sequence Checklist]].