Config file size reduction

[LeXXik]

Didn't want to off-topic the original thread, so moving here from: #5675 (comment)

Thank you for clarification, @Maksims! On that note, I am actually interested in learning your ways. Both the post-processing the config file to split it into smaller chunks and the database approach. Would you mind sharing your wisdom?

We do have a postprocessing step, so it would be easy for us to extend or modify it to support chunks. However, how does it work in practice? I suppose you mark your assets by tags, and then move all assets with the same tag into a separate config file. Then app logic would load the corresponding config chunk when needed. However, how does the app handle it?

As for the database approach - do you mean moving the config data to database, and reading from there, instead of the JSON file?