Right now the File API (as far as I am aware) supports sessions, cache content, temp files, and whatever is in the Moodle data directory (lang packs and whatnot). While this is convenient for poorly written plugins and whatever else, it makes it almost impossible to scale Moodle out efficiently. Is it possible to deprecate temp files, move language packs etc into the core Moodle directory, and setup the File API to throw all user uploaded content (and anything else) into S3 or a CDN? Local storage is the major roadblock to efficiently duplicating Moodle servers.
Caching and sessions are best kept elsewhere anyway, user uploads make more sense in an S3 bucket or some remote alternative, and temp files shouldn't exist in the first place. I suppose this is calling for a complete replacement of the API as it currently is.
1.
|
Move language packs into core directory |
|
Closed | Unassigned |
2.
|
Deprecate temp files from data directory |
|
Closed | Moodle HQ |
3.
|
Remote user uploads and file access |
|
Closed | Unassigned |
4.
|
Relocate other data directory content |
|
Closed | Unassigned |