Open dskaggs opened 5 years ago
one thing i noticed when using your docker with cron when setting the cron to a very low freq like every minute: when i move very large files around, the first process is not finished, so the second cron kicks in and moves the file again, resulting in a duplicate (if overwrite is not set). This problem could also be solved with watched folders given the notifywait waits until the first organize is finished and then runs it again if files have changed in the meantime.
Do you have Organize watch a folder with sub-folders or a single folder where all files reside? In my reading about the inotifywait
feature, it puts watches on all folders under the top-level watch folder to infinite levels. I need to study that a bit to see if that would cause problems with Organize. I can see a potential where more than one sub-folder gets files dropped and multiple copies of Organize get triggered across the entire folder tree.
currently organize watches multiple folders with multiple subfolders in them. i wonder what a good approach would be to integrate that ability?
define which foldersinotifywait
should watch to run organize or parse the yaml to know which folders organize "organizes" and then runinotifywait
on those also?
Add the ability to have the Docker container configured to use Linux's
inotifywait
feature to watch source folders and trigger Organize on file creation.