Hi! I’m building new base images and so finally had a look at JupyterLab 2.1. It looks like the Extension Manger is enabled by default now? Is this intentional, or just a side-product of the large refactor? I ask because it doesn’t seem to be documented.
Since I’m building these bases to run inside Gigantum, it doesn’t make as much sense for the user to configure extensions through the Jupyter UI. I suppose this would be similar to folks running on Binder, JupyterHub or other dockerized Jupyter envs?
We create the user directory at runtime, so to the extent possible, I’d like to avoid needing to create a jupyter config (it’s just one more moving piece). If there were a command-line run-time flag, that’d be a little nicer for my use case. But to recap:
- Is the plan to keep the extension manager enabled by default going forwards?
- If so, what’s the easiest way to configure a jupyterlab isntance to run with extension manager disabled (ideally avoiding writing to user home dir)?