Ian Rose

Which dictionary do you mean? I'm mostly referring to making `IClusterModel` look more like `cluster.scheduler_info`, so that we have to do fewer `if`/`else`/`try`/`except` checks, and more direct copying of the...

Hi @consideRatio (and @stsievert), sorry about the extremely late response. As far as I can tell, you are unable to access your remote dashboard due to [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) and/or [mixed content](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content)...

Thanks for bringing this up @jacobtomlinson. We'll also need to add tokens for pypi/npm.

This is now tested in GH actions. I'll leave this open until we fix up auto-deploy and linting

> thanks @jacobtomlinson, makes sense indeed. Maybe I got a bit too excited with the orange buttons and was hoping the extension would proxy itself ... In the medium-term I...

Thanks for the additional detail @valpesendorfer. I don't expect hot-reloading to work. You will typically need to make sure that the configuration is present before the serve starts up (some...

Beat me to it! Yeah, the location to the image recently changed. We clearly need to get some proxy recommendations in place, but for the moment: CORS policies tend to...

Overall, my preference would be to adapt `dask-labextension` to be able to place nicely with `dask-gateway`, rather than create a fork/separate project. > * Support adding tabs for the dashboards...

> My understanding of @ian-r-rose 's original plan was that Dask-Gateway itself might replace the server-side component in dask-labextension. That way JupyterLab might talk directly to routes on the Gateway...

Sorry for the slow response @dhirschfeld. This is a common issue that people run into (see discussion here: https://github.com/dask/dask-labextension/issues/194). Long-term, I think the right solution is to proxy more stuff...