Files
meteor/tools/runners
Robert Lowe 3332558ddb Introduce MONGO_BIND_IP override (#9606)
* Introduce MONGO_BIND_IP override

Introduces an environment variable (MONGO_BIND_IP) for overriding of meteor's mongod's `bind_ip` option to allow docker containers to bind on `0.0.0.0` to be able to expose mongod processs via docker's `-p 3001:3001` port bindings.

Related issue: https://serverfault.com/questions/758225/cannot-connect-to-mongodb-in-docker
Partially Related PR: https://github.com/meteor/meteor/pull/469

* Use METEOR_MONGO_BIND_IP over ambiguous MONGO_BIND_IP

Change request to use METEOR_MONGO_BIND_IP over ambiguous MONGO_BIND_IP
2018-02-08 10:30:28 -05:00
..
2015-08-10 12:01:21 -07:00

Runners

The Meteor tool process would run multiple big "parts" that should be managed: started, stopped, restarted, monitored for crashes, etc.

The interface that Meteor tool uses is called a "runner".

Some of the runners run sub-processes. The main runner is called run-all, it has sub-runners such as run-app, run-mongo and run-proxy. Other runners are used for different CLI commands.

Run Log

The output of the runners (compilation errors, state change, etc), should be reported through the Run Log. Run Log is also something that users see in their browsers, when their app breaks.