Open b00tsy opened 7 years ago
This is longer maintained, I opened a PR over a year ago to solve the README issue you mention and no one ever replied.
We forked it and made some changes to get it to work properly.
In addition to the linked issue, I found another one -- there's also some nuances with setting up subscribers that this module doesn't get right -- if you call into a redis transports action in a seneca.ready
block, the transport won't actually be ready, you'll get some nasty errors and it won't do anything.
Didn't add an issue here though as -- like you say -- seemingly unmaintained.
I've gone ahead and forked this with my changes inside it --
npm i seneca-redis-transport-fork
I'm currently evaluating the use of seneca, especially with a redis transport. I had a hard time to find out that not I'm stupid, but that the examples given in the readme are wrong (issue #39, probably an issue of seneca or seneca-transport) and that the latest released version is also not working (issue #42). Btw. the readme is also giving a wrong example of how to install this plugin, correct would be
npm install seneca-redis-transport --save
Which is why I'm interested in knowing whether this transport of seneca is still supported or whether I should go for another npm packet or another seneca transport?