search

dask / dask-labextension

JupyterLab extension for Dask
BSD 3-Clause "New" or "Revised" License
311 stars 62 forks source link

mention how to proxy dashbord link in README #183

Open mathause opened 3 years ago

mathause commented 3 years ago

It took a lot of digging to find out how to connect to a dashboard on a remote machine/ jupyterhub instance. Finally I found: https://jobqueue.dask.org/en/latest/interactive.html#configuration and it works well. Could we link to this in the README?

That is the recommended way to connect to a dashboard via jupyterhub? How would a sysadmin best set that up for all users? 

DASK_DISTRIBUTED__DASHBOARD__LINK="/user/{JUPYTERHUB_USER}/proxy/{port}/status"

before starting jupyterhub?

jacobtomlinson commented 3 years ago

That's definitely a valid way to configure this. I would support adding a section to the README. Do you have any interest in raising a PR to add this?

jacobtomlinson commented 3 years ago

Depending on which spawner you are using for Jupyter Hub you should be able to configure environment variables for each Jupyter session.

fperez commented 3 years ago

Big +1 on documenting this a bit more clearly right away in the README, we were just looking at this issue with @consideRatio and eventually the above proved very helpful!

mathause commented 3 years ago

I think I had issues with this because I had an old config file around - now it seems to work without setting the environment variable.

tlvu commented 2 years ago 
DASK_DISTRIBUTED__DASHBOARD__LINK="{JUPYTERHUB_SERVICE_PREFIX}proxy/{port}/status"

Is even better since it will take care of everything in front of /user, if any.

Example on my system:

                "JUPYTERHUB_USER=lvu",           
                "JUPYTERHUB_BASE_URL=/jupyter/",
                "JUPYTERHUB_SERVICE_PREFIX=/jupyter/user/lvu/",