To prevent this, we need to add the version number / the hash of the file content into the file name when we deploy so that it automatically is forced to fetch the new content.
I think having the hash would be ideal so that old files that are the same can still be cached, but the version number may be easier to implement. Either are better than the current situation of users have broken websites upon deploys...
To prevent this, we need to add the version number / the hash of the file content into the file name when we deploy so that it automatically is forced to fetch the new content.
I think having the hash would be ideal so that old files that are the same can still be cached, but the version number may be easier to implement. Either are better than the current situation of users have broken websites upon deploys...