Apply Changes Made to global.js
Opened this issue · 5 comments
Hi there,
I've deployed nodejs-pool && poolui successfully a couple of days ago with following install script
https://github.com/Snipa22/nodejs-pool/blob/master/deployment/deploy.bash#L51
When I do some changes to my pool name in ~/poolui/build/globals.js, I cannot see the new changes on the webpage after refreshing the browser or after doing service caddy restart. It seems to only take effect if I reboot the server.
There is a closed issue about this on the issue tracker from nodejs-pool which suggests to change the checksum on app.manifest which unfortunately doesn't work for me :/
Snipa22/nodejs-pool#78
What is the correct way to apply the changes made to global.js?
Thanks for the support!
It's browser caching imo, nothing else... Deleting the web application cache manually worked for me.
In theory changing app.manifest should force browser to re-download the files but...
thx for the hint - You're awesome :) Worked like a charm after deleting app cache on the browser.
I thought the web server would serve some cached html files :/
Just one thing left on the error list. I just saw on the chrome dev console that I'm receiving
Application Cache Progress event (56 of 83) http://domain.xx/assets/sponsor-logo.png /#/home:1 Application Cache Progress event (57 of 83) http://domain.xx/user/blocks/blocks.js /#/home:1 Application Cache Progress event (58 of 83) http://domain.xx/index.html /#/home:1 Application Cache Error event: Resource fetch failed (4) http://domain.xx/index.html
DOMException: Failed to execute 'update' on 'ApplicationCache': there is no application cache to update.
Is this maybe the reason why I have to delete the cache by hand each time on updating content?
Yes, seems like it. The original ui is unfortunately a bit crude and unfinished... But after some tweaking it is usable.
ok then. I will further investigate and put my results here for the record.