You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I'm currently using shareDB for real-time editor websites.
I scaled up my server using pm2.
Since there are multiple processes, the shareDB is not sharing some of the properties.
I'm also using database adapter sharedb-mongo.
Even if I could fetch the doc object when there is an update from another process, it seems like when one process changes the preventCompose property to serialize ops, another process does not detect the change.
Is there a way to fix this? Any suggestion for this issue?
Thank you.
The text was updated successfully, but these errors were encountered:
preventCompose is a property that exists on the Doc, which is the representation of a client.
As such, you'll have to set this on a per-client basis. If you need to sync this behaviour between clients for some reason, you'll need to do this manually (I guess you could do it through a mini JSON0 document?
Hi,
I'm currently using shareDB for real-time editor websites.
I scaled up my server using
pm2
.Since there are multiple processes, the shareDB is not sharing some of the properties.
I'm also using database adapter sharedb-mongo.
Even if I could fetch the doc object when there is an update from another process, it seems like when one process changes the
preventCompose
property to serialize ops, another process does not detect the change.Is there a way to fix this? Any suggestion for this issue?
Thank you.
The text was updated successfully, but these errors were encountered: