URL asset image doesn't update when changed

Anthias
1

I have added a URL as an asset but when I change the image associated with that URL Anthias still displays the old image.

Any ideas on how to stop this

2

To confirm:
You add an asset that is a URL but it is an URI that ends in an image?
Example: http://www.somewebsite.com/filename.jpg

And when you update that filename.jpg on your server, anthias keeps displaying the old cached image?

3

Yes exactly, although it is a PNG to be specific

4

I dont want to get too much into the ScreenlyWebview (uses QtWebEngine) current config and cache settings because most of that compiled configuration might not be “editable”, I have to get a refresher on the config and its location etc before I can tell you if its possible to change the current caching mode of the ScreenlyWebview browser.

But, in the meantime, if you want to manually delete the current cache, as far as I know you need to go into the container docker exec -it screenly-srly-ose-viewer-1 bash and remove rm -rf all the files in this location:

image
image1291×324 49.4 KB

You might also need to delete cache from the location in the same container in:
.local/share/ScreenlyWebview/QtWebEngine/Default/Local Storage/

I will try to mess around with an idea of creating a symbolic link to /dev/null so that cache folder doesnt really get cached but instead goes into the abyss so every time you load a asset/URL it will not be in the cache thus theoretically load fresh every time, have to see if its even possible.

5

Okay that’s good to know I can just run an hourly cronjob and that should resolve my issue, only problem is I’m having a little difficulty getting that cronjob working

image
image1341×514 36.3 KB

Any Idea why this isn’t working?

6

That is not how you run commands inside a container, the -i is for interactive, which is not something you are doing.

Basically you are looking for something like:

docker exec -d screenly-srly-ose-viewer-1 sh -c "rm -rf /data/.cache/ScreenlyWebview....."

But as I am testing, I think there is another location for session data in /data/.local/.... as well…
I guess you can play around with deleting different folders and not worrying about messing anything up since restarting the container will recreate those temporary directories…