top | item 20163106 (no title) SylvainCorlay | 6 years ago There are some details about this in the blog post. - no execution request is sent by the front-end. - code is stripped out unless explicitely stated otherwise. For deployment, we are working on several scenarios around JupyterHub. discuss order hn newest sandGorgon|6 years ago your blog post still displays the code. Not sure if that can be turned off as well.Please consider the request for a Docker based output build in addition to whatever you do for jupyterhub hobofan|6 years ago From the blog post:> with --strip_sources=False, input cells will be included in the resulting web application (as read-only pygment snippets).So the sources are presumably not there by default.
sandGorgon|6 years ago your blog post still displays the code. Not sure if that can be turned off as well.Please consider the request for a Docker based output build in addition to whatever you do for jupyterhub hobofan|6 years ago From the blog post:> with --strip_sources=False, input cells will be included in the resulting web application (as read-only pygment snippets).So the sources are presumably not there by default.
hobofan|6 years ago From the blog post:> with --strip_sources=False, input cells will be included in the resulting web application (as read-only pygment snippets).So the sources are presumably not there by default.
sandGorgon|6 years ago
Please consider the request for a Docker based output build in addition to whatever you do for jupyterhub
hobofan|6 years ago
> with --strip_sources=False, input cells will be included in the resulting web application (as read-only pygment snippets).
So the sources are presumably not there by default.