Hi,
Firstly, thanks for Binder!
The issue is open on my repo: https://github.com/raybellwaves/dask-sql-binder/issues/4
I copied a repo where I previous had a dask dashboard. The only difference I can see between my two repos are:
When launched it is on notebooks.gesis.org (my previous binder repo was launched on hub.gke2.mybinder and the dask dashboard worked fine).
This repo only has one notebook. Is that why it launched on notebooks.gesis instead of hub.gke2.mybinder?
Can I specify the server to be hub.gke2.mybinder? I believe the dask dashboard will work there.
Thanks,
Ray
According to here , it may indeed work there.
I’ve sent you how to try it in a message. It is best to continue to feature the main Mybinder portal URL as you currently do at your repository because presumably this will be fixed down the road and this way the Binder Team can continue to control traffic as they see fit.
This isn’t needed now as @willirath got the dask dashboard working on both hub.gke2 and notebooks.gesis.
1 Like
manics
October 29, 2020, 5:06pm
4
Thanks for the update! For the benefit of anyone discovering this thread in future see the solution at
Thanks for the fix @willirath . Can see the PR here: https://github.com/raybellwaves/dask-sql-binder/pull/5
FYI. @willirath added the .dask/config.yaml file as
distributed:
dashboard:
link: “{JUPYTERHUB_BASE_URL}user/{JUPYTERHUB_USER}/proxy/{port}/status”
and updated
sed -i -e "s|DASK_DASHBOARD_URL|/user/${JUPYTERHUB_USER}/proxy/8787|g" binder/jupyterlab-workspace.json
to
sed -i -e "s|DASK_DASHBOARD_URL|${JUPYTERHUB_BASE_URL}user/${JUPYTERHUB_USER}/proxy/8787/status|g" binder/jupyterlab-w…
3 Likes