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 (UTC+1), Kwankyu Lee escribió: > > > > 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. In order to make it run I >> just copied the corresponding nbextension folder from the sage install to >> the jupyter folder. >> But when I tried to make it run behind the jupyterhub, graphics don't >> show. >> >> Does somebody have a clue about how things should work in this kind of >> setting? >> > > The clue is that the threejs interactive graphics expects the resource > > /nbextensions/threejs/three.min.js > > available from your domain. Your jupyterhub server should somehow serve > this resource. My comment here > > https://groups.google.com/forum/#!topic/sage-devel/RGwGeJ5Tlso > > would give more clues. > > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
