Title: [BUG] "Folder with Files" node is unusable in Docker due to aggressive Path Traversal validation #5958
Description
Describe the bug
The "Folder with Files" document loader is currently broken for local Docker installations. Any attempt to provide a valid path (absolute or relative) results in an Error: Invalid folder path: Path traversal detected.
This appears to be caused by a recent security update (likely around v3.0.6) that blocks any path containing slashes or dots. While intended to prevent external attacks, it has rendered local file indexing impossible for users mounting local drives (like Obsidian vaults) into Docker containers.
Setup
To Reproduce
Run Flowise via Docker Compose.
Mount a local Windows directory to a container volume (e.g., - "D:/MyNotes:/vault").
Add the Folder with Files node to a chatflow.
Enter /vault, ./vault, or vault into the Folder Path field.
Attempt to "Upsert" or save.
Result: The UI returns "Invalid folder path: Path traversal detected."
Expected behavior
Flowise should allow paths that resolve within the container's mounted volumes, especially when running in a local/standalone environment.
Screenshots
No response
Flow
No response
Use Method
Docker
Flowise Version
Operating System
Windows
Browser
Other
Additional context
Users have spent hours attempting to bypass this by mapping volumes directly into /root/.flowise/vault, but the validator blocks any string containing a /. It also did not work with doing . or vault or any other method. This essentially deprecates the local folder loading feature for the entire Docker user base.