Redis cache confusion

[Sorry_Duh]

I’m getting really lost with Redis and caches in general I’ve looked at a few docs and post but can’t work out some things.

1. how do you refresh/reset the Redis cache for pages (without hard refresh if possible although hard refresh also isn’t working)

2. server connections again how do I refresh them with Redis is this possible?

[George]

This tutorial should explain it all:

PREVIEW: Content Caching for Node.js with Redis

Intro Now you can empower Redis caching service with Docker and select which Node.js pages and API Actions to be cached. Then instead of processing them fully on each request, they will be cached in the super fast Redis memory cache and served so much faster to the clients! This is the perfect Server Side caching for all your web visitors! This will increase your site speed at least 10 times! Note: All this is possible only with Node.js and Docker and it is for now only under the Experimenta…

We should move it the the official docs @Teodor

[Sorry_Duh]

This is actually what I was following which works great to get everything into caches but lets say after cacheing I use a form to add a new item to a database how could I then refresh the cache, same with after caching lets say I add a new element to the page how can I refresh it here too?

I tried both append and persistent options am I using this incorrectly maybe?

[JonL]

It’s not implemented in the UI but if you are ok with coding you could create very quickly a custom module for that.

[Sorry_Duh]

Probably not something I’d be able to do I only know limited code would I be able to set a variable of 0 and use that as a dynamic bind in the settings of Redis on the action if I enter the bind manually?

[JonL]

Don’t have a timeframe but as I’m starting to implement redis in some of my projects I will probably have to create some custom modules for it(including cache clearing).

On the other side I remember @george said something about integrating redis further so it depends how far along the roadmap that is(if it is).

[George]

@Sorry_Duh

This is actually what I was following which works great to get everything into caches but lets say after cacheing I use a form to add a new item to a database how could I then refresh the cache, same with after caching lets say I add a new element to the page how can I refresh it here too?

refreshing cache should work just as refreshing the server connect action for sockets:

Realtime Data Update with NodeJS and WebSockets

Intro Realtime Data Updates are here! Thanks to the NodeJS and Socket.IO integration in Wappler now you can build realtime apps! WebSockets is an advanced technology that makes it possible to open a two-way interactive communication session between the user’s browser and a server. If you want to get updates in real-time, WebSockets allows a persistent connection between your browser and the server. The server is constantly waiting (listening) for new data/information and whenever received, …

You can use the same refresh server action if I’m not mistaken @patrick

[George]

@JonL

On the other side I remember @george said something about integrating redis further so it depends how far along the roadmap that is(if it is).

We have the Redis standard actions as Server Connect actions but a more higher level integration might be needed.

[Sorry_Duh]

This has refreshed the data, doesn’t the live socket refresh do all clients on that page though? I know direct message can do one client but is there a way so only the user who triggers the action gets the update? or am I misunderstanding sockets not really tried them much yet

[Sorry_Duh]

This doesn’t seem to do what im needing it does all clients and then next user to load the page gets the previous users cache

I was hoping I could when a database is edited with specific ids reset caches so that anyone who had viewed for example page 5 would have to renown load the cache but as page 77 had no update the cache would remain for that page