documentcloud/jammit — Issue #208: Production - No Cache busting timestamp on js and css packaged files
Author: designwaves
Created: 2011-10-11 18:40:48+00:00
State: open

I'm using the following
Rails 3.0.9
Jammit 0.6.2
Jammit-s3 :branch aws-s3
Engine yard deployment

I can't seem to figure out why my s3 urls won't add the ?<%mtime%> to the end of the url for js and css packaged assets. It appears to work in development but not in production. All my other assets add the cache busting url param but just not the jammit created ones. Is there something I might need to add to the config or add to my environment for force this? Anyone that can help, please help! I'm stuck here. Thank you so much!