Entrypoint file polls for a Mongo connection forever about meteor-base HOT 5 CLOSED

Is it possible that the mongodb package isn't getting installed and available globally?

The deprecation warning in your output comes from that package. But it was never intended to be available globally, it's installed under the folder where that script is run.

from meteor-base.

Oh, I'm not worried about the deprecation warning. But the fact the docker-compose up command never makes it past the Mongo check is a bit frustrating. Could it be a race condition of some sort?

from meteor-base.

Yes, that's why the script is there to poll until Mongo is ready. The Node container usually starts up faster than Mongo in my experience.

from meteor-base.

Right, but what I'm saying is the poll never ends. It just polls and polls and polls…

from meteor-base.

Oh, good lord, I think I figured it out. I had a misconfigured port, so I wasn't able to access the app. For some reason, the "Starting app…" message never appeared in my console, so while the app was running, it was just inaccessible. Could I suggest adding a console statement inside the connect-to-mongo.sh declaring a successful connection? Might help when reviewing logs in the future. Something like:

const mongoClient = require('mongodb').MongoClient;
setInterval(function() {
  console.log('Polling for Mongo connection…');
  mongoClient.connect(process.env.MONGO_URL, function(err, client) {
    if (client) {
      console.log('Mongo connected.');
      client.close();
    }
    if (err) {
      console.error(err);
    } else {
      process.exit(0);
    }
  });
}, 1000);

A bit odd that the "Starting app…" message never pops up — not sure why that's happening. Sorry for the confusion.

from meteor-base.