I observe that after rebuilding the jitsi-meet project, clients can use immediately the new code when accessing to the URL. But sometimes clients need clear browser-cache (by pressing Ctrl-Shift-R) in order to have the latest code version.
My question is that modifying which components in the meet-jitsi project requires such manual cache-clearing? Can I use some tricks (embedding some timestamps ) to automate such clearing procedure ?
Before pushing the changes to the server, you can modify index.html
sed -i.bak -e "s/app.bundle.min.js?v=[[:digit:]]*/app.bundle.min.js?v=$VERSIONMIN/" index.html sed -i.bak -e "s/lib-jitsi-meet.min.js?v=[[:digit:]]*/lib-jitsi-meet.min.js?v=$VERSIONMIN/" index.html sed -i.bak -e "s/all.css/all.css?v=$VERSIONMIN/" index.html
And then push libs + index.html.
This is what the ci job does for every new version of jitsi-meet debian package.
Dear @damencho ,
Thank you for your hints.
I wonder whether I should set the $VERSIONMIN to the modified timestamp of the associated js file to make sure they will be downloaded automatically?
Put anything that is different from previous times you add it. We pit there an incrementing build number fro the ci job.