From 28fff48e0ae84aeea4f536d37c51f3414adc90ec Mon Sep 17 00:00:00 2001 From: Brian Di Palma Date: Fri, 17 Jul 2020 08:31:50 +0100 Subject: [PATCH] Updated Downloads and Importing (markdown) --- Downloads-and-Importing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Downloads-and-Importing.md b/Downloads-and-Importing.md index c173c5d..3850e7f 100644 --- a/Downloads-and-Importing.md +++ b/Downloads-and-Importing.md @@ -22,7 +22,7 @@ Incorrect path issues are possible too, though less common in normal setups. The The default user for a Windows service is **SYSTEM** which typically doesn't have access to your shares. Edit the service and set it up to run as your own user, see the FAQ entry [why can't Sonarr see my files on a remote server](https://github.com/Sonarr/Sonarr/wiki/FAQ#why-cant-sonarr-see-my-files-on-a-remote-server) for details. ## Mapped network drives are not reliable -While mapped network drives like `X:\` are convenient, they aren't as reliable as UNC paths like `\\server\share` and they're also not available before login. Setup Sonarr and your download client(s) so that they user UNC paths as needed. If your library is on a share, you'd make sure your root folders are using UNC paths. If your download client sends to a share, that is where you'll need to configure UNC paths since Sonarr gets the download path from the download client. It is fine to keep your mapped network drives to use yourself, just don't use them for automation. +While mapped network drives like `X:\` are convenient, they aren't as reliable as UNC paths like `\\server\share` and they're also not available before login. Setup Sonarr and your download client(s) so that they use UNC paths as needed. If your library is on a share, you'd make sure your root folders are using UNC paths. If your download client sends to a share, that is where you'll need to configure UNC paths since Sonarr gets the download path from the download client. It is fine to keep your mapped network drives to use yourself, just don't use them for automation. ## Docker and user, group, ownership, permissions and paths Docker adds another layer of complexity that is easy to get wrong, but still end up with a setup that functions, but has various problems. Instead of going over them here, read this wiki article [for these automation software and Docker](https://old.reddit.com/r/usenet/wiki/docker) which is all about user, group, ownership, permissions and paths. It isn't specific to any Docker system, instead it goes over things at a high level so that you can implement them in your own environment.