-
-
Notifications
You must be signed in to change notification settings - Fork 525
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow serving Flask apps #1215
Allow serving Flask apps #1215
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1215 +/- ##
==========================================
- Coverage 87.61% 87.48% -0.14%
==========================================
Files 106 106
Lines 12574 12601 +27
==========================================
+ Hits 11017 11024 +7
- Misses 1557 1577 +20
Continue to review full report at Codecov.
|
Wow. As a potential user of this I would like to learn what the best deployment strategi is for different use cases. Panel on Bokeh server? And can I run Panel, Flask and the tranquilizer api on all those servers? How will they perform? What are the pros and cons? This raises many questions. Can I use all the Flask functionality? For example can I build advanced rest apis using Flask extensions with open api documentation? Can I serve dynamic files using Flask? Would it be a good idea to mix flask and panel to a large extent? Could I embed Panel apps in the Flask apps I serve? And how? And whats the architecture. Is the flask server running. Or is the flask app running on Tornado? Running on multiple servers as well as in notebook is a super power. But currently not documented and experiences not shared. Request: Some kind of documentation and examples. :-) |
Yes, we have funded work to document deployment options, so it's definitely coming. |
As one specific point among many that need documentation, if you used |
No that explicitly does not work, flask apps may only be served on a subpath. |
Well it was certainly beyond my ability to route things, might give that another go. |
Ok, I now see that in the code "Flask apps must be served on a subpath.". Definitely needs explaining, then... |
This looks very very cool....looking forward to seeing some examples! |
This is really cool! However, I also wanted to serve a Tornado app alongside So, for future comers to this thread, you can pass extra Tornado |
@philippjfr |
Allows serving flask app using pn.serve, e.g.:
This will serve the panel app on
localhost:5001/panel
and the flask app onlocalhost:5001/flask/app
.