mirror of
https://github.com/meteor/meteor.git
synced 2026-05-02 03:01:46 -04:00
This is a developer experience (DX) change. In production, the `METEOR_SETTINGS` environment variable is used to pass parameters which will be available in the `Meteor.settings` within the app. However, `METEOR_SETTINGS` is ignored when using the `meteor-tool` itself as in development, environment variables are often less desirable. Additionally, there would be no reactivity when changing settings was necessary, instead requiring that the `meteor` tool be restarted entirely. On more than one occasion, developers have been confused as to why the `METEOR_SETTINGS` are not respected in development. To make it more clear when this is attempted (and clarify that they will _not_ be used), provide the a clear warning before ignoring the `METEOR_SETTINGS` variable. Aims to avoid meteor/meteor#8455.
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.