You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 18, 2022. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: