Due to cms-user errors, huge images, broken renditions, duplicated content or whatever we should have a permanent look at the size of the tar files for all collections.
What would be an easy (and project independent) solution?
Most likely the logic / statistic tracking should be implemented via wagtail-to-ion, and the project logic handles how this information is used / who is able to see this information (e.g. sending alarm emails via custom, project related triggers / adding a statistic panel to the wagtail dashboard etc...
New settings like ARCHIVE_MAX_FILE_SIZE_INIT / ARCHIVE_MAX_FILE_SIZE_DELTA would be useful to specify thresholds depending on project requirements
Due to cms-user errors, huge images, broken renditions, duplicated content or whatever we should have a permanent look at the size of the tar files for all collections.
What would be an easy (and project independent) solution?
Most likely the logic / statistic tracking should be implemented via wagtail-to-ion, and the project logic handles how this information is used / who is able to see this information (e.g. sending alarm emails via custom, project related triggers / adding a statistic panel to the wagtail dashboard etc...
New settings like ARCHIVE_MAX_FILE_SIZE_INIT / ARCHIVE_MAX_FILE_SIZE_DELTA would be useful to specify thresholds depending on project requirements