Replies: 1 comment
-
|
So I configured multi-instance again with Redis cache handler, and re-checked what is the behavior. And so it's pretty strange... When I open admin for the first time, admin bar shows that preview mode is active, and as before, after a single change "Exit preview mode" in admin bar disappears, even without the change applied :[ I also started getting this error when I reload the admin page (no error when only preview frame is reloaded): Update:I now confirmed by scaling down to 1 instance, that issue is not in cache handler or live preview installation, but in the multi-instance :/ So I guess the only thing is that the live preview doesn't work between instances... How can this be solved? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
I have issues with live preview when I run multiple instances of Payload with Next's cacheHandler configured (
@trieb.work/nextjs-turbo-redis-cachein particular) (I'm running multiple instances in Docker usingdeploy.replicas)I will explain the issue (I did not create an issue because I don't get how to create a reproduction URL with multiple instances & Redis cacheHandler, sorry...):
When I open any admin page edit, live preview works (admin bar has "Exit preview mode"), then after making a single change to any input, live preview frame is reloaded with the change, however the "Exit preview mode" disappears, and live preview no longer works :(
After reloading the admin page, everything is the same... (I believe sometimes it doesn't work even after reload, and sometimes works again for a single change, I will recheck that).
I think this looks like after change, live preview reloads the frame, and the frame gets routed to other instance of Payload where live preview can't work like that, between instances...
I wonder if I even need multiple instances, or should I just run a single payload instance on a machine, without Docker?
I'm concerned that the images seem to load slower (as if sequentially) when running only one instance. Is that correct? Or
node server.jsis able to handle multiple requests at once?Beta Was this translation helpful? Give feedback.
All reactions