emizzle f5c77b1416

Process logs API refactor ...

There are three separate instances of process log APIs: embark logs, blockchain logs (when in standalone mode), and child process logs (storage, communication, blockchain, etc). Each one was repeating the implementation of creating a process log API endpoint. This commit centralises the API declaration by using the class `ProcessLogsApi`.

`ProcessLogsApi` is started for all three components mentioned above: blockchain (in standalone) in the `BlockchainListener` module, embark in the `EmbarkListener` module, and for all child processes in the `ProcessLauncher`.

These listeners have two functions:
1. Create the process logs API endpoints for `get` and `ws`, and
2. Ensure that all logs are logged through the `LogHandler`, which normalises the output of the log and ensures each log has a timestamp and id (used in the cockpit for log ordering).

Also, this commit moved the pipeline in to a module, so that the `embark` object could be passed to the `ProcessLogsApi` (to be used for registering API endpoints).

2018-10-25 13:04:28 +02:00

..

babel-loader-overrides.js

feat(modules/pipeline): move pipeline into its own module plugin

2018-10-22 19:35:58 +02:00

index.js

Process logs API refactor

2018-10-25 13:04:28 +02:00

webpack.config.js

use a customized require/.resolve instead of relying on NODE_PATH

2018-10-22 19:54:49 +02:00

webpackConfigReader.js

Clean up

2018-10-22 19:54:49 +02:00

webpackProcess.js

Do not run webpack for file changes that do not need webpack

2018-10-22 19:54:48 +02:00