Files
meteor/tools/runners
Seba Kerckhof 9c9a8263ab Add separate SERVER_NODE_FLAGS envar (#10965)
* Add separate SERVER_NODE_FLAGS envar

Since Meteor 0.5.3, Meteor allowed to pass node command line flags
to the server node process via the `NODE_OPTIONS` environment variable.

However, since Node version 8 / Meteor 1.6 this has become a default node
envar with the same behavior:
https://nodejs.org/api/cli.html#cli_node_options_options

The side effect is that this now also affects Meteor tool.

The command line parameters could already be set separately via the `TOOL_NODE_FLAGS` envar.
This is now also possible (again) for the server.
2020-04-17 20:17:53 -04: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.