Mirrors/Radarr
1
0
Fork 0
mirror of https://github.com/Radarr/Radarr.git synced 2024-07-04 11:07:59 +02:00
Code Issues Releases Wiki Activity

Updated Users Guide (markdown)

Donald Webster 2020-05-04 21:27:33 -07:00
parent 8f8b0b2c80
commit 35cd9d8230
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Users-Guide.md

@ -34,6 +34,6 @@ But now we come to torrent clients, and my opinion of them is that there are non
You've done the hard part, you've selected your download client and indexers/trackers. Now we move on to the next task, which is getting your library and download folder sorted out to be the best it can be. From a very high level, Radarr is going to need to be able to read and write to both folders. Your download client will also need to be able to read and write to the download folder. If you have an existing library of movies you're going to import, it will need to be in the right structure which is a `movie.ext` file in a `movie/` folder which is in a folder of `movies/`, like `movies/Movie Title (Year)/Movie Title (Year).ext`. Ideally, the movie file name will also contain the *quality/source* (like DVD, HDTV, WEB-DL or BLURAY), edition (Theatrical, Director's Cut, Unrated) and/or `-GrouP`. All of this information is irreplaceable, it cannot be found any other way. So if you have that data, make sure it is in the file name.
Ideally, your download folder is on the same file system as your library folder. This will allow imports that *move*, like usenet and torrents that are *finished seeding* to be instant and it allows hard links for imports that *copy*, like torrents that are still seeding when imported. For moves, it saves time and io which *most* users won't really notice... but for long term seeding, hard links allow a library and download copy to exist without wasting space. If you want to download to a different drive or file system, like an SSD, you can still achieve this by having your *incomplete* folder on the SSD, but your *complete* folder on the library file system.
Ideally, your download folder is on the same file system as your library folder. This will allow imports that *move*, like usenet and torrents that are *finished* seeding, to be instant and it allows hard links for imports that *copy*, like torrents that are *still* seeding. For moves, it saves time and io which *most* users won't really notice... but for long term seeding, hard links allow a library and download copy to exist without wasting space *and* the download folder can be a hot mess while the library folder is nice and neat. If you want to download to a different drive or file system, like an SSD, you can still achieve this by having your *incomplete* folder on the SSD, but your *complete* folder on the library file system.
I would also suggest separating your downloads logically, putting usenet downloads in one folder and torrents in the other. And inside those download folders, consider category based sub-folders too. For example, `/data/usenet/{tv|movies}` and/or `/data/torrents/{tv|movies}`. I like to *avoid* naming the folders after the software itself, since I don't know what the future might hold where I switch from one to another and then end up in the awkward situation of using SABnzbd pointed at a folder named `nzbget`.
I would also suggest separating your downloads logically, putting usenet downloads in one folder and torrents in another. And inside those download folders, consider category based sub-folders too. For example, `/data/usenet/{tv|movies}` and/or `/data/torrents/{tv|movies}`. I like to *avoid* naming the folders after the software itself, since I don't know what the future might hold where I switch from one to another and then end up in the awkward situation of using SABnzbd pointed at a folder named `nzbget`.