Live data from Hacker News

Voilà turns Jupyter notebooks to standalone web applications

blog.jupyter.org

21–30 of 52 posts

Re: Voilà turns Jupyter notebooks to standalone web applications

#21
post #12

Is there any work on bringing Python into the browser like with JavaScript? At the beginning of the year, I was looking at the best way of making an interactive textbook either with Python (requiring a backend it seemed), or with JavaScript via D3. You can still use Jupyter Notebooks with JS; there's a library called BeakerX by Two Sigma that does this. I went the D3 route but it was hard to stay motivated when most…

Check out Metatron Discovery(https://metatron.app) They have jupyter notebook connection feature. And it is open source. Here is the github repo: https://github.com/metatron-app/metatron-discovery

Re: Voilà turns Jupyter notebooks to standalone web applications

#23
post #10

Earlier quoted context omitted.

What do you mean? Jupyter notebooks are usually pure Python apart from (sometimes) interactive widgets, which have Javascript behind them since it's in a browser. I don't think this is much use without widgets, so maybe you mean something else?

I mean why can't I write python outside of jupyter and generate these dashboards? Or can I?

[deleted]

Re: Voilà turns Jupyter notebooks to standalone web applications

#25
post #10

Earlier quoted context omitted.

What do you mean? Jupyter notebooks are usually pure Python apart from (sometimes) interactive widgets, which have Javascript behind them since it's in a browser. I don't think this is much use without widgets, so maybe you mean something else?

I mean why can't I write python outside of jupyter and generate these dashboards? Or can I?

If you want to avoid Jupyter Notebooks you can look into Dash or Bokeh Server.

Jupyter is convenient though :)

Re: Voilà turns Jupyter notebooks to standalone web applications

#26
post #4

Earlier quoted context omitted.

I've been using the Jupyter AppMode plugin for a few years, it has been very useful for internal tools. Voilà looks similar, with more sheen, it's going to enable true rapid SPA development.

Voila author here: a major difference with AppMode is that AppMode is merely hiding the notebook interface, but still allows for arbitrary code execution. Voila is meant for producing secure web apps.

hi - its very interesting that you talk about security. what's the deployment story here ?

in fact, now that i think of it - can you generate an output folder with a Dockerfile ? so a mere docker build will produce a running docker compatible "build" folder ?

Also, can you have a mode where you hide the source code ? i just get the output data ? for world viewable dashboards.

Re: Voilà turns Jupyter notebooks to standalone web applications

#27

Earlier quoted context omitted.

Voila author here: a major difference with AppMode is that AppMode is merely hiding the notebook interface, but still allows for arbitrary code execution. Voila is meant for producing secure web apps.

hi - its very interesting that you talk about security. what's the deployment story here ? in fact, now that i think of it - can you generate an output folder with a Dockerfile ? so a mere docker build will produce a running docker compatible "build" folder ? Also, can you have a mode where you hide the source code ? i just get the output data ? for world viewable dashboards.

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.

Re: Voilà turns Jupyter notebooks to standalone web applications

#28

Earlier quoted context omitted.

hi - its very interesting that you talk about security. what's the deployment story here ? in fact, now that i think of it - can you generate an output folder with a Dockerfile ? so a mere docker build will produce a running docker compatible "build" folder ? Also, can you have a mode where you hide the source code ? i just get the output data ? for world viewable dashboards.

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.

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

Re: Voilà turns Jupyter notebooks to standalone web applications

#30
post #29

side note: I hope everyone is aware of Jupyter Lab , the successor of Jupyter Notebooks -- it's been basically version 1.0 for over a year: https://blog.jupyter.org/jupyterlab-is-ready-for-users-5a6f0...

...a lot of us are practically addicted to Jupyter Notebook Extensions [1] features and these aren't compatibly with Jupyter Lab and Jupyter Lab didn't add equivalent builtin features.

Once you get used to little things like (a) auto-TOC/outline of current doc in a sidebar (with highlight for current running cells and other goodies), (b) auto scroll to end of output, (c) browser notifications for end of long running calculations (so you can be alerted of stuff being done while browsing in other tabs) etc. etc. you really can't live without them!

It's this little things that matter 100x more than freely rearrangeable tab-grids and detachable outputs and terminals... these are cool but it's the other small details that make a bigger difference in productivity!

(As someone who also has some frontend web experience I was planning to maybe try and code these and contribute, but I never find the time, and last time I looked I couldn't find a good entry point to start learning about jupyter lab's frontend code...)

[1] https://github.com/ipython-contrib/jupyter_contrib_nbextensi...

Post reply on HN