Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not working with socket.io-redis-emitter #8

Open
dzeroone opened this issue Nov 24, 2023 · 3 comments
Open

Not working with socket.io-redis-emitter #8

dzeroone opened this issue Nov 24, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@dzeroone
Copy link

I have tried to emit from a cronjob, but it's not reaching the client!

@darrachequesne
Copy link
Member

Yes, the Redis emitter is meant to be used with the classic Redis adapter, we will have to implement a custom emitter publishing to the Redis streams.

@darrachequesne darrachequesne added the enhancement New feature or request label Nov 27, 2023
@fjeldstad
Copy link

Yes, the Redis emitter is meant to be used with the classic Redis adapter, we will have to implement a custom emitter publishing to the Redis streams.

Is this something that is planned?

@fjeldstad
Copy link

fjeldstad commented Sep 3, 2024

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants