Replacement of the internal file storage

Replacement of the internal file storage

by Steffen Pegenau -
Number of replies: 1

Hey guys!

To connect our Moodle with other services, we want use an central file server. So far, not a big problem with all the available repository plugins. But
- the files are to be stored only on the file server (Usually Moodle loads the files from the external server (for example Dropbox) and stores it in its own storage system, right?)
- the synchronization should work on both ways, one can upload/move/delete files in Moodle AND on the file server
- every file (drag ‘n drop or file-picker) should be uploaded directly to the file server.

Can a repository plugin fulfill these conditions? Or is there any other modular way?

At the moment, the file server triggers the creation of a modified url activity after a change is made on the file server. Next step for us would be the file upload in moodle. We thought about using a repo with an iframe, to load the upload-form of our file server. After the upload to the file server, moodle is triggered, a url is created and we simply have to reload the course to see the changes. Not a nice solution, but it's getting even worse, if we will have to change the dragndrop-libs to get that working, too.

Could you think of a better solution?

Thanks for every response!

Average of ratings: -
In reply to Steffen Pegenau

Re: Replacement of the internal file storage

by sam marshall -
Picture of Core developers Picture of Peer reviewers Picture of Plugin developers

Hi,

We've done a couple of experimental repository plugins which work by moving files out of the Moodle filesystem on cron. In other words, upload (or any other way of adding files, such as programmatically adding them) works just like normal to the moodle filesystem. Then, for affected files, we automatically move them into a repository (if they don't already exist).

That way, files will be temporarily located on Moodle filesystem for about half an hour (if your cron runs every half-hour) but then moved out..

We didn't do this for the same reason as you; this was in an attempt to move large files or those from a specific component out of the Moodle filesystem so that they can be handled separately in order to organise disk storage.

This hasn't gone live on our system and so I can't say for certain there won't be problems with it. Also, don't know if this approach applies to your situation or not! But it does generally seem to work (as a way to still use normal upload feature but store files elsewhere) so thought I'd mention it.

--sam