As per issue #301 I have now managed to sync a remote gcode folder with the watched folder on multiple clone printers. OctoPrint picks up the new files, moves them about and PrintTimeGenius then analyses them (GREAT :-) ).
But, because OctoPrint moves (emptying the watched folder) all the files out of watched and replaces uploads with them, this means PrintTimeGenius runs on every file. This is not the end of the world, but means I can't run rsync as a scheduled task, as will re-write files that are currently printing.
It also results in an unnecessary amount of overhead, as PrintTimeGenius now re-analyses "new" files that it had technically analysed before.
I am just wondering if this is the best workflow? Is there a better solution? I checked the wiki but couldn't see anything that looked relevant.
As per issue #301 I have now managed to sync a remote gcode folder with the watched folder on multiple clone printers. OctoPrint picks up the new files, moves them about and PrintTimeGenius then analyses them (GREAT :-) ).
But, because OctoPrint moves (emptying the watched folder) all the files out of watched and replaces uploads with them, this means PrintTimeGenius runs on every file. This is not the end of the world, but means I can't run rsync as a scheduled task, as will re-write files that are currently printing.
It also results in an unnecessary amount of overhead, as PrintTimeGenius now re-analyses "new" files that it had technically analysed before.
I am just wondering if this is the best workflow? Is there a better solution? I checked the wiki but couldn't see anything that looked relevant.