Details
-
Improvement
-
Status: In Progress
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
This is a low hanging fruit. Currently the content repository is set via a database configuration table. It would be better and more consistent to move this to application.properties instead. Dependency injection best practices are not followed, so we would improve that too and have - as a nice side effect - less files to deal with, no more database dependency and users could develop more custom content repositories.
While we are at it: remove the unnecessary distinction between "files" and "images"... and within images: no need to distinguish between client, staff or any other image for that matter.
Provide a migration tool to import existing legacy files/images into the new repository format.