On Sunday, April 28, 2019 at 8:23:13 PM UTC+2, Song Liu wrote: > > So that actually I am looking for a deployment separation between "static > (html,js)" and the backend server, where: > > - the web server provides the viewing and editing (+ save to storage) > function > - the backend server is created on demand for running >
There's Jupyter Kernel Gateway and Jupyter Enterprise Gateway for running kernels remotely. The nb2kg component ties a notebook server to the remote kernels. I don't know if there's something similar for JupyterLab already, or if nb2kg works there as well. You should keep in mind though that notebook extensions will not work in this scenario. The extensions that users install are put on the backend server running the kernels, but the browser will try to fetch the static files of the extensions from the web server. cheers, Roland -- 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/76412942-a3f6-4cf0-a1b7-d46c420a500d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
