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
Users may experience problems after upgrading reef-pi since browsers cache static content. This issue can be fixed by using a cache busting scheme during the production webpack build. This should solve the problem of asking users to make sure they clear their cache after upgrade.
The text was updated successfully, but these errors were encountered:
I don't have any implementation in mind. I think HASH is a typical solution, but I have not researched any alternatives.
We can use HASH for release number / revision. Depends on how you want to implement it. Also http server can handle it too. But in our case the best is hash or revision. I'm taking care of it.
Users may experience problems after upgrading reef-pi since browsers cache static content. This issue can be fixed by using a cache busting scheme during the production webpack build. This should solve the problem of asking users to make sure they clear their cache after upgrade.
The text was updated successfully, but these errors were encountered: