In fact, it was one of the edge-cases mentioned in. Not having a periodic scan forces you to move to a more event-driven approach, which is what we're trying to achieve here.īTSync is somewhat of an tricky edge case, coz afaik it has no 'finished' event. Personally I call my folder processing, but anything to distinguish it as not drone would be better. I know this is just semantics, but it does muddy the waters. Calling the directory drone confuses the issue since we are specifically doing away with the drone folder. That way Sonarr can't see partial files or incomplete directories.Ī remote mount is preferable, but not mandatory. Picture of Set DNA symbol, Document folder, Video graphic card, UAV Drone, Robot, Router and wifi signal, Smartwatch and Robotic robot arm hand factory icon. The directory names you have chosen are confusing. For example by transferring to a temp directory and then moving that directory to the import folder, or simply signal Sonarr when it's ready. The goal is to ensure that the entire set of files appear in the directory at a whole (atomically). I believe drone factory folder is slated for the chopping block in Sonarr, that might trickle down into Radar eventually too.
DRONE FACTORY FOLDER DOWNLOAD
Despite your mentioning 'no file system access' I'm still gonna say it, but isn't it possible to mount it via sshfs? Why are you using drone factory folder Completed download handling is really the way you want to set it all up, let it talk to the download client to coordinate everything.This allows any external process to signal Sonarr that the download is ready to be imported. The Sonarr API, you can call the Sonarr API to have it import a specific directory and optionally specify the original download identifier so Sonarr knows which download it is about.Remote Path mapping, this generally applies to any remote mount, but can also be used if you use a transfer method that's 'atomic', more on that later.So I'm going to give you the general gist until I get some more details. There are a few ways to tackle this, but it depends on how you currently handle the transfer. Question: You mentioned that the files are moved to Server A 'via some process', on which computer is that process initiated and is it a script that you can adapt? This current warning is to move people away from it, and prevent new users from (mis)using it. The Periodic Drone Factory scan will be removed in v3 (we're at v2 now) and won't happen in any automatic update. We get a significant amount of support request from users that misuse it and don't even need it. The reason we don't want people to use the Drone Factory is because it's very easy to get it wrong and get partial files, partial imports and what not.
0 kommentar(er)
