From c0abd2f84e5e13cdfcddfbf7c29503bb20196be1 Mon Sep 17 00:00:00 2001 From: Achilleas Pipinellis Date: Sun, 5 Jul 2020 19:27:13 +0200 Subject: [PATCH] Fix typo of "Mappings" --- readme-vars.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/readme-vars.yml b/readme-vars.yml index 0244edb..d8a920e 100644 --- a/readme-vars.yml +++ b/readme-vars.yml @@ -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: