Gibbs Consulting

Apologies, managed to overlook this. For sure `WrappedDash` looks like it could be split along these lines, although I think you'd first have to check the use of anything in...

There is already async handling in [jupyter-plotly-dash](https://github.com/GibbsConsulting/jupyter-plotly-dash)

The relevant documentation is [here](https://django-plotly-dash.readthedocs.io/en/latest/updating.html#live-updating) - it is certainly sparse and any contributions to improve it are most welcome. It is not clear to me why you've had to explicitly...

@007ebey what is `PLOTLY_APPS`? Have you established that your custom component works correctly from a vanilla Dash application? That can be a useful way of locating where the problem lies.

The database/driver has some [limitations](https://github.com/microsoft/mssql-django#limitations) which are in conflict with the `django_plotly_dash` codebase. If switching to a better-supported database (Postgresql is a much better fit with Django, basically) is not...

As of #402 `django-plotly-dash` should now work for Dash 2.0 and higher

Ideal outcome: `serve_locally` works as expected (this should already be the case for component constituents) assets can be added as per the standard Dash approach for [external resources](https://dash.plot.ly/external-resources)

This is also related to #95

@hungpl2 does your application successfully redirect from other (non django-plotly-dash) pages? And is login_oauth on the same server or a different one?

@eddy-ojb the main one is that it should be possible to run just uvicorn for all requests in production, whereas Daphne was just being used for the pure asgi part...