disable locally

[macrozone]

Issues include as much detail as possible:

I noticed that when you have no redis locally, it logs some connection error to redis, but the app is in an unkown state: publications work, but they won't be reactive.

As redis oplog is a production improvement, its nice to be able to test it, but it should not be a requirement that every developer needs to run it locally.

Is it possible to disable it locally so that it fallsback to meteors normal behaviour?

[edemaine]

If I'm reading the code correctly, it will do nothing if redisOplog isn't in settings.json (and no REDIS_OPLOG_SETTINGS environment variable is set). So if you're testing locally via meteor (without --settings settings.json), or if you use a non-Redis settings.json, you should be able to test locally with Redis.

However, if you have the disable-oplog package installed, you also won't get oplog tailing in your local dev server. (I'm guessing this is what #274 was getting at.) But it still works, maybe just not as fast.

But see #357 when using fine-tuning.