Add support for globs to `bokeh serve`

I have been working on a way to make it easier to use panel serve to launch deployments at a proxied port on jupyter notebook calls, so that your deployment shows up at localhost:8888/panel. I’ve got this working for cases where you have a dir with one notebook in it called main.ipynb, but I’d like to have it look at all the notebooks and generate an index. This would be equivalent to calling panel serve *.ipynb but using a flag instead. The reason for the flag is that it isn’t possible to pass the * in the proxy code:

'command': ["panel", "serve", ".", "--allow-websocket-origin=*", "--port", "{port}", "--prefix", "{base_url}panel"],

For context this functionality would make it very easy to deploy apps on binder. The user would just need to include jupyter-panel-proxy in their env and stick ?urlpath=panel at the end of the binder url.

These are the relevant PRs:

• https://github.com/pyviz/jupyter-panel-proxy/pull/1
• https://github.com/pyviz-demos/glaciers/pull/11

If we were able to add the --all-notebooks flag, then I’d be happy to write a jupyter-bokeh-proxy as well 😃

[jsignell]

Ah sorry yes that is true. Ok I am good with the suggestion.

[bryevdv]

that changes the default behavior on a feature that we are using in long-lived projects. Is that really preferable?

I don’t think it does? Currently we always get shell globbing for

bokeh serve *.py

And we always will—we have no ability to affect or turn off shell globbing. My understanding of this issue is that it is desirable that (effectively) this also work:

bokeh serve '*.py'  

for cases when this might arise (e.g. calling a subprocess without shell=True) But that it does not currently work. So the proposal (as I understand it) it to allow

bokeh serve --glob '*.py'  

which would do globbing manually when:

• the --glob flag is passed
• the arg that is passed has a literal * in it

This would not affect normal command line usage AFAICT, but would allow globs passed in subprocess calls to behave as expected.