You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a default (not locally installation) we could allow JupyterLab Native to connect to binder. Here is an issue on the binder hub repo that is discussing the proposed API for starting a binder instance with a a REST API.
Here is a rough sketch:
* We need a REST API end point to hit that 1) starts the binder, and 2)
returns the URL of the running instance with any security token needed to
connect.
* We would then hit the REST end point, grab the URL+token and point
JupyterLab at it.
* Would be helpful to get the url and token base separately as JSON
* If the instances timeout, it would be helpful to have a way to query if
the instance is still running or if we have to restart. or that, it might
be helpful to have the REST end point take the URL from an existing
instance and return the running one or a new one at that URL.
--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
[email protected] and [email protected]
As a default (not locally installation) we could allow JupyterLab Native to connect to binder. Here is an issue on the binder hub repo that is discussing the proposed API for starting a binder instance with a a REST API.
jupyterhub/binderhub#13
@yuvipanda
The text was updated successfully, but these errors were encountered: