What does changing config.assets.version number do?

Question

I understand that the assets expire (as it is written in the comments) but what does it do in the background?

would it delete all the compiled assets? or does it take that version number and uses it somewhere else?

FYI that as of right now this is broken for Sprockets >= v3.0. (The default for new Rails applications). See also [this other stackoverflow question](http://stackoverflow.com/questions/32548755/rails-4-2-rails-application-config-assets-version-doesnt-invalidate-digest-asse) and [this sprockets-rails github issue](https://github.com/rails/sprockets-rails/issues/240). — Jordan Brough, Dec 03 '15 at 01:11

score 12 · Accepted Answer · answered Nov 01 '12 at 15:50

12

It will precompile assets with another fingerprints (the code appendend to the file name), making all the client's browsers download the files again.

In other words, as you said, it expires the caches in the client's browsers.

answered Nov 01 '12 at 15:50

hsgubert

would it delete the older assets from the server (on heroku)? – Nick Ginanto Nov 01 '12 at 15:56
2

Humm, I don't know about Heroku, but deploying with Capistrano the precompiled assets are deleted and regenerated on every deploy. – hsgubert Nov 01 '12 at 15:58

1 Answers1