With my aproach there is no need of an extra apache server. The jupyterhub
server takes care of that.
I guess that my patch would conflict with the standard use (without
jupyterhub). So in order to include it in the main branch we would need a
way to distinguish if we are running through jupyte
On Sunday, March 4, 2018 at 1:17:40 AM UTC+9, mmarco wrote:
>
> Thanks, I finally could solve it with a dirty hack:
>
> I put the nbextensions inside /usr/local/share/jupyter/hub/static/
>
I did the same.
> jupyterhub does serve files that are located there
>
Right, at /hub/static/. So I
Thanks, I finally could sole it with a dirty hack:
I put the nbextensions inside /usr/local/share/jupyter/hub/static/
(jupyterhub does serve files that are located there) and patched sage to
serve those file from /static/... instead of /nbextensions/...
El viernes, 2 de marzo de 2018, 7:05:27
On Friday, March 2, 2018 at 12:30:29 AM UTC+9, mmarco wrote:
>
> I am trying to install a service to use Sage through the jupyterlab
> frontend, behind a jupyterhub server.
>
> So far, I could get everything to work, even the threejs interactive
> graphics on a standalone jupyterlab instance. I
