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:34:00 -07:00
parent 35cd9d8230
commit ffbe0cf08e
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Users-Guide.md

@ -36,4 +36,8 @@ You've done the hard part, you've selected your download client and indexers/tra
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 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`.
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`.
Your library folder should be the easiest to setup, you'll need root folders which will hold the movie folders which will hold the movie files. You can have as many root folders as your heart desires, but you'll need to *manually* select the right one when you're adding a movie, so keeping this to a minimum is wise. I use `Movies`, `Kids Movies`, `Anime Movies` and `Documentary Movies` and feel like this is a good number. I would *not* want a root folder for each letter of the alphabet. I would also not want a root folder for every genre. They would both have too many and selecting the right one when adding a movie would be a chore.
Finally, ownership and permissions of these folders. If you're using Windows, this should be easy since you'll be using one user for everything. Just make sure any services are running as *your* user instead of the default, which is `SYSTEM`. On Linux/Unix, a *proper* setup would be an [eponymous](https://www.lexico.com/en/definition/eponymous) user per daemon and a shared group with a umask of `002`. It would also be acceptable and simpler to use a *single* user setup here with a umask of `022` or `002`, but it isn't best practices. I have no idea what that will look like on MacOS, but suspect it'll be closer to the single user Windows style setup.