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
Are there any significant drawbacks of just creating a dummy socket.io server with the redis-streams-adapter configured and using emit on that server instance to send events from background processes (like the cron job mentioned in the original post)?
I've tested this locally both with the old redis-adapter and this redis-streams-adapter and as far as I can see it works well; no need to call listen(...) or anything, just create a server instance and emit 🤷 Seems too good to be true! Is it?
I have tried to emit from a cronjob, but it's not reaching the client!
The text was updated successfully, but these errors were encountered: