Hi,
when I upload video files in the courses module in the MongoDB database, "Download" -> fs.files and then in the fs.chunks table program add binary data split to maximum MongoDb size. I have a few questions related to this process and logic:

1. In the administrator panel, I can change the files to be stored in the file system and not in the database. Does this not apply to the course module files?
2. After removing the video file from the lesson, the whole lesson, or even the entire course, the entries in the fs.files and fs.chunks tables remain. Which, with a large number of videos files, can be problematic. Is this a problem where I will have to write supervisor or a plugin that cleans the database from unnecessary binary data? Is there any scheduler that monitors and cleans tables?

Best regards
Michael

According to the first question, setting in the Media settings is used only for pictures, they will appear in the wwwroot folder, to be publicly available. In the case of videos used in courses, if you make them stored in the file system, you will make them available without purchasing products. I suppose it won't be expected behavior for you.

In the case of second question, I think it's a default behavior of GridFS in MongoDB, and every operation inside should be done by a database administrator directly in the database. We don't interfere in it by the application.

saving to the file system does not have to be a wwwroot folder. Files can be stored in a dedicated folder for courses with aappool or www-data write read permission. It is then streamed through the controller to the end user. As for the second part, I disagree. MongoDB is a non-relational database and it is a big mistake to leave unnecessary large binary data like video files in tables.

WebArgo wrote:

Yes, and no :) It has to be wwwroot folder because it is how it's done now. We don't have a plan to modify this functionality now.

In the case of GridFS, you're right. We made some additional research and internal analysis, and we definitely should handle it during the "Delete" operation. I've made a task for developers here, we will try to implement it in the incoming version.  

Thanks you for the quick reply.