I’ve just put a pretty substantial laminas-mvc project into production, assuming it would be easy to turn on application configuration caching. My recollection, last time I did this, was that all you had to do was provide the right answers in
'config_cache_enabled' => true, 'config_cache_key' => 'application.config.cache', 'module_map_cache_enabled' => true, 'module_map_cache_key' => 'application.module.cache', 'cache_dir' => 'data/cache',
and that did the trick. I’ve read https://docs.laminas.dev/laminas-mvc/services/#application-configuration-options and it doesn’t seem to say otherwise. I thought there was a way to set this up with pure configuration. Then I started reading https://docs.laminas.dev/laminas-config-aggregator/caching/ but I still don’t understand what code goes where in order to make file-based caching happen. It seems to be either failing silently, or not even trying.
I hope this is enough information but if it isn’t, slap me and I’ll try harder.
Any ideas? Thanks.