This page: https://jupyterlab.readthedocs.io/en/stable/user/urls.html
mentions URLs like e.g.
<lab-location> here ? do I get to configure that ?
I’m asking because we have an architecture in place with an nginx reverse proxy as a frontdesk
this assumes a static partitioning of the URL space, and as part of that we assume jupyterlab-served urls always start with
but this doc suggests otherwise; or am I misreading this ?
Can someone please shed some light on this
lab-location thing, I have not found where it is explained in readthedocs
as a side question, I’ve asked this on gitter earlier, am trying my luck again here
is there a general rule to pick one medium or the other ?
I think it depends on how you’re running jupyterlab. If you’re running standalone lab-location will be just
/, if you’re using jupyterhub then lab-location will be a combination of where jupyterhub is running and a user-id e.g.
/hub/username, and in either case if you’ve got a proxy you might choose to run them under a custom /prefix (can’t remember what the configuration properties are).
OK, thank you for that information, it is helpful
I don’t use jupyterhub so I take it this is going to be empty for me then;
IMHO it is kind of odd that jupyterlab’s documentation accounts for extra addressing bits that are actually managed by another, optional, layer of tooling ?
It is a recognition that JupyterLab does not exist in isolation, but often is used in conjunction with other tools.
I’ve also been trawling the documentation to see if there is a way to change this setting due to reverse proxy situation… to no avail.
jupyter lab --help-all for the
base_url setting. For example:
jupyter lab --ServerApp.base_url='/mybaseurl'