mirror of
https://github.com/linuxserver/docker-radarr.git
synced 2026-02-03 16:34:37 +08:00
Fix typo of "Mappings"
This commit is contained in:
parent
187e71dd94
commit
c0abd2f84e
@ -48,7 +48,7 @@ app_setup_block: |
|
||||
|
||||
**Special Note**: Following our current folder structure will result in an inability to hardlink from your downloads to your movies folder because they are on seperate volumes. To support hardlinking, simply ensure that the movies and downloads data are on a single volume. For example, if you have `/mnt/storage/Movies` and `/mnt/storage/downloads/completed/Movies`, you would want something like `/mnt/storage:/media` for your volume. Then you can hardlink from `/media/downloads/completed` to `/media/Movies`.
|
||||
|
||||
Another item to keep in mind, is that within Radarr itself, you should map your torrent client folder to your radarr folder: **Settings -> Download Client -> Advanced Settings -> Remote Path Pappings**. The input the host of my download client (matches the download client defined) remote path is `/downloads/Movies` (relative to the internal container path), and local path is `/media/downloads/completed/Movies`, assuming you have folders to seperate your downloaded data types.
|
||||
Another item to keep in mind, is that within Radarr itself, you should map your torrent client folder to your radarr folder: **Settings -> Download Client -> Advanced Settings -> Remote Path Mappings**. The input the host of my download client (matches the download client defined) remote path is `/downloads/Movies` (relative to the internal container path), and local path is `/media/downloads/completed/Movies`, assuming you have folders to seperate your downloaded data types.
|
||||
|
||||
# changelog
|
||||
changelogs:
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user