Master list of Flask features we're missing about dashr

[chriddyp]

I've tried to keep the list of flask specific things as small as possible.

• Auth is hand-rolled (https://github.com/plotly/dash-auth) with standard HTTP stuff and cookies
• Dash-Python uses gzip but that can be done on the server layer too
• Dash-Python optionally serves files locally instead from CDNs - alternative implementations will need to be able to serve files
• Deployment for R should be able to use https://github.com/virtualstaticvoid/heroku-buildpack-r/tree/heroku-16 for heroku and Plotly On Prem deployment

AFAIK, users are only accessing the underlying web server (app.server) to:

• Add additional HTTP routes like static file serving
• Access the requests cookies (we can use this to allow developers to access the username of the logged-in viewer)

[cpsievert]

@chriddyp I'm not super familiar with Flask, so if you think there is anything that is absolutely essential that may not be obvious from studying the dash ecosystem, please let me know!

[cpsievert]

Great, seems like most of things are already doable given @thomasp85's fiery/routr/reqres framework.

[thomasp85]

Yeah - there're no deal breakers here - I'm planning to add standard authentication tools to firesafety, but if js dash uses a custom setup this will just have to be made custom in R as well...

fiery supports, automatic packing, unpacking of bodies using gzip, deflate, and brotli

fiery has no problem serving static content and routr even has a plugin route for mapping URL paths to subdirectories...

I have no experience with heroku so here we'll have to experiment - I cannot see why there should be any problems though (famous last words)