Skip to content
This repository has been archived by the owner on Mar 18, 2022. It is now read-only.

Asset versioning in production #99

Open
assafweinberg opened this issue Mar 1, 2016 · 1 comment
Open

Asset versioning in production #99

assafweinberg opened this issue Mar 1, 2016 · 1 comment

Comments

@assafweinberg
Copy link

This might be a silly question, but I noticed that in non-production mode, there's a ?v=[timestamp] at the end of each asset, but in production mode its always ?v=0. This seems to mean that every time I deploy new code, I also have to manually invalidate the cache to get the new assets loading in production. Is that right, or should production assets also have a ?v=[timestamp] and automatically be updated without invalidation?

@gagalago
Copy link
Contributor

Is that fixed in 0.2.9 ?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants