I'm interested in using the "kernel_gateway" (https://github.com/jupyter/kernel_gateway) for re-architecting an existing Notebooks application, but I'm confused whether "kernel_gateway" supports my use case. All I really need is a headless notebook server. I already have a simple UI for adding/removing cells, executing code, etc. I just want it to interact with a remote API (REST/WS is fine) for all notebook/kernel operations.
I've been reading these posts trying to get a better idea if the kernel gateway is the answer: http://blog.jupyter.org/2016/03/09/jupyter-kernel-gateway/ https://github.com/jupyter-incubator/proposals/blob/master/kernel_gateway/proposal.md In the first post, it says it provides a "100% Jupyter Notebook server compatible API", but I'm not able to see any evidence of an API for notebooks (e.g. insert cell, update cell, etc.). All I see are 2 modes of operation: "notebook_http" (which let's you expose notebook cells as REST endpoints) and "jupyter_websocket" (which let's you communicate directly to kernels via WS instead of 0mq). Of course I could still use the "kernel_gateway" for the WS to 0mq functionality, but I think I would have to manage the state/formatting of the .ipynb myself (which I'm hoping to avoid). Should I just host a Jupyter Notebook Server and simply hide all of the UI endpoints that I don't need? -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/a40994fb-889a-40d0-b569-fd2d2a8db7ff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
