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
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+. 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!
Warning: It's very important you get this exactly right. The host should be all lowercase and the paths are case sensitive. Failure to set these mappings or do them correctly will cause other issues.
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.