Server application used to connect an enchannel-socketio-backend to a Jupyter kernel.
To install kernel relay run
npm install -g kernel-relay
Kernel-relay should be installed on the same machine that the Jupyter kernels are installed on. After it's installed, run it using
kernel-relay
In order to communicate with a kernel over the web, you either need to expose raw ZeroMQ sockets or translate to another layer which is friendly to most networking environments. The Jupyter Notebook uses direct websockets. This project, kernel-relay, connects to a kernel and relays ZMQ communications across socketio sockets. This allows web applications to use Jupyter kernels with socketio instead of ZMQ. kernel-relay includes a minimal RESTful API for managing kernel life cycles.
kernel-relay was designed to be used with enchannel-socketio-backend.
The CLI for kernel-relay is:
kernel-relay [port]
Kernel-relay's HTTP RESTful API listens on port 3000 by default.
The RESTful API for spawning a kernel follows:
/spawn/[kernelSpecName]
The response is a JSON string. The success message contains the kernel's ID:
{
"id": string
}
If an error occurs, the response is HTTP status 500 containing a JSON string with error information:
{
"error": string
}
Example:
$ curl localhost:3000/spawn/python3
{"id":"d6f3beac-c8d3-489b-af64-b1e91dba0ad7"}
The RESTful API for shutting a kernel down follows:
/shutdown/[id]
The response is a JSON string. The success message contains the kernel's ID:
{
"id": string
}
If an error occurs, the response is HTTP status 500 containing a JSON string with error information:
{
"error": string
}
Example:
$ curl localhost:3000/shutdown/d6f3beac-c8d3-489b-af64-b1e91dba0ad7
{"id":"d6f3beac-c8d3-489b-af64-b1e91dba0ad7"}
Socket.io connections are available at the following endpoints by kernel ID:
/shell/[id]
/stdin/[id]
/iopub/[id]
/control/[id]
The following is an example of how to connect to the shell channel using socket.io:
const io = require('socket.io-client');
const shell = io.connect('http://localhost:3000/shell/d6f3beac-c8d3-489b-af64-b1e91dba0ad7');
To develop against kernel-relay, first clone the repo then from within the cloned folder run:
npm install
npm link
Before opening a pull request, please run the unit tests locally:
npm test