Support for recursive scanning

[golyalpha]

Now, I could add this feature, and I am going to work on this, but I still felt like this should be tracked with an issue (to separate discussion about the feature from discussion about the code itself). Also, no promises on me actually getting it done. (Seriously, most of my work is in Python and JS. Don't judge.)

Basically, the idea is to add an option for plot paths to be scanned recursively.

It would add another option for the "type" property, "recursive".
That way, a path to multiple drives/mountpoints containing plotfiles could be defined as:

{
"path" : "/media/plots",
"type" : "recursive"
}

Where the contents of /media/plots could be:

/media/plots
 - drive1
 - drive2
.
.
.
 - driven

Obviously this path definition can result in an increased overhead on scanning, if used incorrectly. But, if used correctly, it could provide a better setup option for miners.

Note that this isn't something that only Linux would benefit from - Windows supports mounting to file paths of an existing drive as well (a feature that is not exploited as often as it should be, in my opinion).

[Creepsky]

Good idea, nice feature.
Suggestion: instead of "type": "recursive" a new field like "recursive": true/false would be better.
That way you can write something like:

{
    "path" : "/media/plots",
    "type" : "parallel",
    "recursive" : true
}

or

{
    "path" : [
        "/media/plots-a",
        "/media/plots-b"
    ],
    "type" : "sequential",
    "recursive" : true
}

[golyalpha]

True, it would allow control over how the files are read and how the files are discovered.

By the way, in the second example, you wouldn't even have to define the paths like that, since recursive mode would scan all subdirs of media for plot files. (Admittedly, a bad mountpoint choice if you have other devices that you connect to the rig and want to use the recursive mode)