Bot Updating Documentation

pull/12/head
LinuxServer-CI 2020-04-24 09:46:35 -04:00
rodzic 887f3ec363
commit 47e230e0a3
1 zmienionych plików z 3 dodań i 1 usunięć

Wyświetl plik

@ -133,8 +133,10 @@ In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as bel
## Application Setup
Access the webui at `<your-ip>:8989`, for more information check out [Sonarr](https://sonarr.tv/).
Special Note: Following our current folder structure will result in an inability to hardlink from your downloads to your TV folder because they are on seperate volumes. To support hardlinking, simply ensure that the TV and downloads data are on a single volume. For example, if you have /mnt/storage/TV and /mnt/storage/downloads/completed/TV, you would want something like /mnt/storage:/media for your volume. Then you can hardlink from /media/downloads/completed to /media/TV.
Another item to keep in mind, is that within sonarr itself, you should then map your torrent client folder to your sonarr folder: Settings -> Download Client -> advanded -> remote path mappings. I input the host of my download client (matches the download client defined) remote path is /downloads/TV (relative to the internal container path) and local path is /media/downloads/completed/TV, assuming you have folders to seperate your downloaded data types.
Another item to keep in mind, is that within sonarr itself, you should then map your torrent client folder to your sonarr folder: Settings -> Download Client -> advanced -> remote path mappings. I input the host of my download client (matches the download client defined) remote path is /downloads/TV (relative to the internal container path) and local path is /media/downloads/completed/TV, assuming you have folders to seperate your downloaded data types.
## Docker Mods