What's the best way to handle asset cache busting in a ZF2 app?
I had a look at the AssetManager module, but it doesn't look like it supports cache busting, although Assetic does have a CacheBustingWorker.
Even if it did support cache busting, what would I do in my layouts to use production assets instead of development?
In the past I've used phing to do the javascript and css minfication, then rename them to include a timestamp, and then update my layouts to use the new version. AssetManager can replace half of that process by building the initial asset files for me, and I could then use a build tool to do the cache busting in a second pass.
Is this method, or something like it still the best way to go, or is there a better way that I'm not aware of?
Cheers, David -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
