mirror of https://github.com/meteor/meteor.git synced 2026-05-02 03:01:46 -04:00

Files

Ben Newman 38096aafc8 Use --debug instead of --debug-brk for meteor debug.

Breaking on the first statement in the program used to be the only way to
get the debugger to stop at any breakpoints, but more recent versions of
node-inspector (compatible with Node 4) do a much better job of stopping
at breakpoints after the program starts.

2016-08-11 18:36:05 -04:00

README.md

mention run-log in runners' readme

2015-08-10 12:01:21 -07:00

run-all.js

Initial IPv6 support

2016-06-06 02:17:36 +03:00

run-app.js

Use --debug instead of --debug-brk for meteor debug.

2016-08-11 18:36:05 -04:00

run-log.js

Don't allow logs to yield to avoid missing logs when the app quits

2016-05-25 18:23:28 -07:00

run-mongo.js

Don't try and use wired tiger on 32bit linux

2016-07-29 13:19:14 +10:00

run-proxy.js

Don't call nonexistent writeHead method of net.Socket objects.

2016-06-27 10:02:37 -04:00

run-selenium.js

Eliminate Future from tools/run-selenium.js.

2015-12-09 12:06:48 -05:00

run-updater.js

Use async functions to eliminate the need for fiberHelpers.inBareFiber.

2015-12-09 12:06:51 -05:00

README.md

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.