Re: [jupyter] Restrict Endpoint Access

2019-04-17 Thread Simon Biggs
This seems to be hitting a similar set of aims to what scripedforms set out to do, except you have managed to focus on security and support Jupyter widgets. Would you be open to me marking scripedforms as deprecated and point users to your repo/package? -- You received this message because

Re: [jupyter] Restrict Endpoint Access

2019-04-17 Thread Jonathan Larkin
That should be: docker run --detach --name appmodesrv --restart always -v /srv/jupyterhub/home/prod:/tmp/working -w=/tmp/working -p : -it mysingleuserserver jupyter notebook --no-browser --allow-root --ip="0.0.0.0" --notebook-dir=/tmp/working --NotebookApp.token=''"

Re: [jupyter] Restrict Endpoint Access

2019-04-17 Thread Jonathan Larkin
I have a similar problem to Alex (a small team, limited dev resources, limited experience in front end dev, etc. and about 10 users who consume the output). I note that Alex mentioned *JupyterHub*. I would imagine this is a very common problem. I am jealous of R/Shiny for this kind of workflow. I

Re: [jupyter] Restrict Endpoint Access

2019-04-17 Thread Chris Holdgraf
Hmmm, I've only ever followed the instructions here: https://github.com/quantstack/voila#installation if those don't work, try opening an issue in the voila repo? I'm sure they'd appreciate feedback on what's confusing! On Wed, Apr 17, 2019 at 9:30 AM Alexander Feiszli wrote: > Thank you

Re: [jupyter] Restrict Endpoint Access

2019-04-17 Thread Alexander Feiszli
Thank you Chris, that is exactly what we are looking for as well, disabling the ability to run arbitrary code. Do you happen to have the instructions for installing and enabling the extension handy? I'm not getting it quite right. On Wednesday, April 17, 2019 at 11:17:56 AM UTC-5, Chris

Re: [jupyter] Restrict Endpoint Access

2019-04-17 Thread Chris Holdgraf
More specifically - one of the goals of Voila is to be more secure. A good default for this is to prevent the user from running arbitrary python code, and keeping their interaction at the javascript layer (which is what widgets are all using). You can find a few cool examples here:

Re: [jupyter] Restrict Endpoint Access

2019-04-17 Thread Tim Paine
Widgets are enabled Tim Paine tim.paine.nyc > On Apr 17, 2019, at 12:07, Alexander Feiszli wrote: > > Also, it says the notebook is "Read Only" in the docs. I would still like > users to be able to provide input datasets via widgets. Is this disabled? > >> On Wednesday, April 17, 2019 at

Re: [jupyter] Restrict Endpoint Access

2019-04-17 Thread Alexander Feiszli
Also, it says the notebook is "Read Only" in the docs. I would still like users to be able to provide input datasets via widgets. Is this disabled? On Wednesday, April 17, 2019 at 10:51:51 AM UTC-5, Alexander Feiszli wrote: > > That's exactly what I'm looking for! > > I'm trying to figure out

Re: [jupyter] Restrict Endpoint Access

2019-04-17 Thread Alexander Feiszli
That's exactly what I'm looking for! I'm trying to figure out how to use this now; there's very scant documentation which makes this a little difficult. I'm running: pip install voila jupyter nbextension install voila and get FileNotFoundError: [Errno 2] No such file or directory: 'voila'

Re: [jupyter] Restrict Endpoint Access

2019-04-17 Thread Chris Holdgraf
Check out Voila! ( https://github.com/QuantStack/voila) I bet that you'd find it interesting - it's quite similar to app mode :-) On Wed, Apr 17, 2019 at 6:54 AM Alexander Feiszli wrote: > Hello, > > At my org we are looking to implement Jupyter notebooks in production as > sort of "mini-apps"

[jupyter] Restrict Endpoint Access

2019-04-17 Thread Alexander Feiszli
Hello, At my org we are looking to implement Jupyter notebooks in production as sort of "mini-apps" for small groups of end users. The idea is that the data scientists can develop in Jupyterhub like an IDE and then push a notebook into a CICD workflow, and then out pops a production version