I’ve been pointing my
meteor instances at an existing
$ MONGO_URL=mongodb://localhost:27017/some_db meteor
mongod is written to by processes external to
meteor, and I want
meteor to pick up those changes and update the page instantly.
Debugging this, I noticed that when I let
meteor start its own
mongod, and have my external processes connect to and modify that,
meteor does update things instantaneously (which is awesome).
I’m guessing that
meteor sets up some oplog-tailing that I am missing with my external
I think I can get by for now having
meteor manage the
mongod in this way, but wanted to document this since I couldn’t find any since-1.0 info about what behavior was expected, and at first I thought that the 10s delay was the best I was going to get.
If anyone wants to chime in about how to glue an external
meteor in a way that makes this work, that would also be cool. Thanks!