Extent "excludePattern" from file/folder level to path level

[z624391]

Great job, it's already amazing how much functionality and great performance you provide within MinimServer. 100k files is no issue for MinimServer!
I just will wait for your update postings.

[simoncn]

This change is now available in MinimServer update 268. You should be to do what you want by setting the excludePattern property to this:

/share/CACHEDEV1_DATA/Music Library/## ROEL ##

[z624391]

Thx Simon.
When I scan: /share/CACHEDEV1_DATA/Music Library
And exclude: /share/CACHEDEV1_DATA/Music Library/Qobuz/
Than it ends up with no exclusion.
The standard Qobuz folder exclusion is working.
Do I misunderstand the excludedPattern working?

[simoncn]

I have not tested with / at the end of the path. Please try this and let me know whether it works:

/share/CACHEDEV1_DATA/Music Library/Qobuz

[z624391]

I just tested it without success. I also restarted the QNAP MinimServer App.

The standard folder exclusion works well with and without the "/" at the end.

So, it feels like your new functionality is not activated.

[simoncn]

Thanks for letting me know. I see what is causing this. I should be able to fix it tomorrow.

[simoncn]

This is fixed now in MinimServer update 269.

[z624391]

Simon, your exclude filter is working. This is what I did:

contentDir:
/share/CACHEDEV1_DATA/Music Library
/share/CACHEDEV1_DATA/Music Library/foobar2000/## ROEL ##/

excludePattern:
/share/CACHEDEV1_DATA/Music Library/foobar2000/## ROEL ##

This is causing a trick:
"foobar2000/## ROEL ##/" is excluded from "/share/CACHEDEV1_DATA/Music Library" but "/share/CACHEDEV1_DATA/Music Library/foobar2000/## ROEL ##/" is still there.
The suffix "/" is important in this case.

Is it maybe an idea to move the excludePattern to the contectDir area (they are strongly related) and create sets of them per item:
1x content + 1x excludePattern
1x content + 1x excludePattern
1x content + 1x excludePattern
etc

[simoncn]

I have checked carefully and there is no difference with having a / at the end of the path in either contentDir or excludePattern.

Also, excludePattern does not exclude content directories. This has always been true for pattern match excludes and it is also true for folder path excludes. This is why /share/CACHEDEV1_DATA/Music Library/foobar2000/## ROEL ## is being scanned even though it is in excludePatterns.

I understand why you are suggesting combining contentDir and excludePattern settings but I think this creates too much complexity. All users need to set contentDir but very few users need to use excludePattern to do what you are doing. Keeping excludePattern as a separate property means that most users don't need to understand the complicated rules for how it works.

[z624391]

Apology for the delayed response, I was on a trip. Your update is working, indeed with or without "/". Thx for your support in this matter.