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

Files

Ben Newman ab338d6cd8 Don't call meteorDebugFuture.wait() unless METEOR_INSPECT_BRK is set.

Bug fixed: we should never be calling meteorDebugFuture.wait() in
production, so we now use process.env.METEOR_INSPECT_BRK in developement
to enable the waiting.

Lesson learned: if you call Fiber.yield() in the only running Fiber
without any other events scheduled on the event loop, the program will
immediately exit with code 0, as it should.

Closes #8817.

2017-06-19 14:32:52 -04:00

README.md

mention run-log in runners' readme

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

run-all.js

Add option to skip release check (#7445 )

2016-08-17 14:53:27 -04:00

run-app.js

Don't call meteorDebugFuture.wait() unless METEOR_INSPECT_BRK is set.

2017-06-19 14:32:52 -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

Update node-mongodb driver to 2.2.16

2016-12-29 20:06:56 +01: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.