You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior
File uploads should respect the storage settings passed in via env variables (ie either BLOB_STORAGE_PATH if using local storage or the S3_* variables).
And multer will try to create the destination directory if passed as a string and if it does not exist:
Note: You are responsible for creating the directory when providing destination as a function. When passing a string, multer will make sure that the directory is created for you. https://www.npmjs.com/package/multer#diskstorage
There seems to already be some functionality for getting the right paths elsewhere:
Yep, I think we should definitely change the hard coded multer path to either whatever env variables that was set, if not, default to the hard coded path
Describe the bug
Flowise uses a hard coded folder path for some file uploads. This breaks on read-only file systems and cannot be configured.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
File uploads should respect the storage settings passed in via env variables (ie either
BLOB_STORAGE_PATH
if using local storage or theS3_*
variables).Setup
Additional context
Hardcoded paths are here:
Flowise/packages/server/src/routes/attachments/index.ts
Line 8 in d057129
Flowise/packages/server/src/routes/openai-assistants-vector-store/index.ts
Line 7 in d057129
Flowise/packages/server/src/routes/predictions/index.ts
Line 8 in d057129
And
multer
will try to create the destination directory if passed as a string and if it does not exist:There seems to already be some functionality for getting the right paths elsewhere:
Flowise/packages/server/src/controllers/get-upload-path/index.ts
Line 4 in d057129
The text was updated successfully, but these errors were encountered: