mirror of
https://github.com/Sonarr/Sonarr
synced 2024-12-22 15:56:58 +00:00
Add download client clearing items
parent
125eb875a4
commit
9cad35058d
1 changed files with 4 additions and 1 deletions
|
@ -26,3 +26,6 @@ While mapped network drives like `X:\` are convenient, they aren't as reliable a
|
||||||
|
|
||||||
## Docker and user, group, ownership, permissions and paths
|
## 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.
|
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
|
||||||
|
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.
|
Loading…
Reference in a new issue