mirror/Sonarr
1
0
Fork 0
mirror of https://github.com/Sonarr/Sonarr synced 2024-12-22 07:43:01 +00:00
Code Issues Releases Wiki Activity

Updated Downloads and Importing (markdown)

Donald Webster 2020-07-11 13:33:55 -07:00
parent f096620059
commit e1ce8a8ab2
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
Downloads-and-Importing.md

@ -28,4 +28,7 @@ While mapped network drives like `X:\` are convenient, they aren't as reliable a
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. 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.
## Download Client Clearing Items ## Download Client Clearing Items
The download client should *not* be responsible for removing downloads. Usenet clients should be configured so they *don't* remove downloads from history. Torrent clients should be setup so they *don't* remove torrents when they're finished seeding (pause or stop instead). This is because Sonarr communicates with the download client to know what to import, so if they're *removed* there is nothing to be imported... even if there is a folder full of files. The download client should *not* be responsible for removing downloads. Usenet clients should be configured so they *don't* remove downloads from history. Torrent clients should be setup so they *don't* remove torrents when they're finished seeding (pause or stop instead). This is because Sonarr communicates with the download client to know what to import, so if they're *removed* there is nothing to be imported... even if there is a folder full of files.
## Download Folder and Library Folder not Different Folders
The download client should download into a temporary-ish folder and Sonarr should import from that into your Library folder. If you download right into your library folder, you'll end up with multiple copies of episodes and when there are import issues, you may not notice because your media server will see the download client copy. The download folder will also be a hot mess of poorly named folders and files while your library folder will be nice and neat.