Remote Path Mappings

📂 Click Here - Sign up for Google's Suite for Business - Unlimited Space

📂 Click Here - NZB's with from NewsHost - PG Members Receive a 58% Discount

Table of Contents

1. Intro
2. Setting Up Via Sonarr
3. Setting Up Via Radarr
4. Summary

---

1. Intro

Downloader mappings tell radarr, sonarr, and [lidarr]] where to look for downloads on your server. PG utilizes these mappings to enable hard linking. Files will process almost immediately with these mappings and with PG 8.3+.

2. Setting Download Mappings in Sonarr/Radarr/Lidarr

For each downloader you use, you need to setup a remote mapping per downloader. A mapping is required per downloader for hardlinking to work. The container must be deployed or it will refuse to save due to the path not existin. Only setup what you have deployed or intended to deploy!

Here is an example:

host: nzbget
remote path: /mnt/downloads/nzbget
local path: /mnt/unionfs/nzbget

host: qbittorrent
remote path: /mnt/downloads/qbittorrent
local path: /mnt/unionfs/qbittorrent

Note: if you have your downloader on a different server, then change the host to nzbget.mydomain.com and leave the rest the same.

4. Summary

Easy and simple to deploy! Visit the forums for further assistance!