-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
disableMongo configuration for Vent-only mode #363
base: master
Are you sure you want to change the base?
Conversation
@edemaine thanks. I had a test and it works perfectly! |
@edemaine This is perfect timing, I was wanting to use Vent but wasn't quite ready to switch to full mongo redis-oplog. I have already done a quick test and it works great. Thanks. |
I would rather use the verbose version ( "extendMongoCollection: bool") + you also have to add to the documentation about a "Vent Only Solution". the problem with this is that we have |
@edemaine could you please finish it? |
@theodorDiaconu OK, I did the suggested rename -- that is a better name. I also added a small section to Keep in mind that |
Right, |
@ramezrafla I want to use only Vent because another features require a lot of time to refactor project. So, I’ll adopt project step by step. |
@theodorDiaconu seems like @edemaine finished the work. Could you please review and merge it? |
We'll have to fix the tests. To be able to merge. |
I have been using this option for a couple of years now on some prod apps, its great for real-time redis data through ddp and Vent. It would be nice to get it into the next release. |
Adds a
disableMongo
configuration option for disabling all the Mongo overrides, but still connecting to the Redis server, which I gather from #359 and #361 is useful for just using Vent.I thought about naming this
overrideMongo
to parallel the oldoverridePublishFunction
(and can change if desired), but given #357, I feel like it could be helpful to override Mongo even when Redis isn't being used, so felt like this was a more accurate name.Fix #359, fix #361, and sort of relevant to #323.