I've used Bokeh with great success in a few demonstrations with
real-time graphs. The setup I've used was a locally running bokeh-server
and a script based on the animated.py example.
Now I would like to place one of these on a public website. What is the
prefered way of doing that currently? Running bokeh-server on a publicly
accessible port seems to be a bad idea. If not for other reasons, then
because anyone can click the "recycle bin" icon in the interface and
delete the plot.
I'm not very picky regarding how the plots are shown. I've used
autoload_server() previously to embed live plots in a
statically-generated HTML page. However, I need to push data from a
Python script to the browser, so doing animation on the browser side in
Javascript is not an option.
If you embed a plot using autoload_server, you should still be able to push data from a python process to the server, and have the plot update. Are you saying this is not happening? If so, please give a bit more info as that is either a bug or some misconfiguration that we should probably address in the docs.
I've used Bokeh with great success in a few demonstrations with
real-time graphs. The setup I've used was a locally running bokeh-server
and a script based on the animated.py example.
Now I would like to place one of these on a public website. What is the
prefered way of doing that currently? Running bokeh-server on a publicly
accessible port seems to be a bad idea. If not for other reasons, then
because anyone can click the "recycle bin" icon in the interface and
delete the plot.
I'm not very picky regarding how the plots are shown. I've used
autoload_server() previously to embed live plots in a
statically-generated HTML page. However, I need to push data from a
Python script to the browser, so doing animation on the browser side in
Javascript is not an option.
If you embed a plot using autoload_server, you should still be able
to push data from a python process to the server, and have the plot
update. Are you saying this is not happening? If so, please give a
bit more info as that is either a bug or some misconfiguration that
we should probably address in the docs.
Oh, sorry. I just checked and embedded plots indeed keep updating even
after they have been deleted from the bokeh-server web interface. I'm
not sure why I thought otherwise.
So from the standpoint of security there should be no issue with running
a publicly accessible bokeh-server?
Thanks
Tomaž
Hi everyone
I've used Bokeh with great success in a few demonstrations with
real-time graphs. The setup I've used was a locally running
bokeh-server and a script based on the animated.py example.
Now I would like to place one of these on a public website. What is
the prefered way of doing that currently? Running bokeh-server on a
publicly accessible port seems to be a bad idea. If not for other
reasons, then because anyone can click the "recycle bin" icon in
the interface and delete the plot.
I'm not very picky regarding how the plots are shown. I've used
autoload_server() previously to embed live plots in a
statically-generated HTML page. However, I need to push data from
a Python script to the browser, so doing animation on the browser
side in Javascript is not an option.
This story isn't really great right now - Bokeh has 2 backends right now for authentication - single and multiuser. With single user, everyone can see everything, so hosting things like that will work - but you don't have security. The multi user case has security but no notion of publishing, and so other users can't see the plots that you create.
Adding access controls around publishing is on the roadmap but isn't implemented yet.
···
On Thu 11 Dec 2014 11:49:36 AM EST, Tomaž Šolc wrote:
Hi Bryan,
On 11. 12. 2014 14:41, Bryan Van de Ven wrote:
If you embed a plot using autoload_server, you should still be able
to push data from a python process to the server, and have the plot
update. Are you saying this is not happening? If so, please give a
bit more info as that is either a bug or some misconfiguration that
we should probably address in the docs.
Oh, sorry. I just checked and embedded plots indeed keep updating even
after they have been deleted from the bokeh-server web interface. I'm
not sure why I thought otherwise.
So from the standpoint of security there should be no issue with running
a publicly accessible bokeh-server?
I've used Bokeh with great success in a few demonstrations with
real-time graphs. The setup I've used was a locally running
bokeh-server and a script based on the animated.py example.
Now I would like to place one of these on a public website. What is
the prefered way of doing that currently? Running bokeh-server on a
publicly accessible port seems to be a bad idea. If not for other
reasons, then because anyone can click the "recycle bin" icon in
the interface and delete the plot.
I'm not very picky regarding how the plots are shown. I've used
autoload_server() previously to embed live plots in a
statically-generated HTML page. However, I need to push data from
a Python script to the browser, so doing animation on the browser
side in Javascript is not an option.