Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update HPC instructions for Jupyterlab version 3 #815

Merged
merged 4 commits into from
Mar 2, 2021

Conversation

rsignell-usgs
Copy link
Member

Jupyterlab version 3 no longer needs to have extensions installed separately. Hurrah! Also the config file with the password is now in ~/.jupyter/jupyter_server_config.py instead of ~/.jupyter/jupyter_notebook_config.py.

Jupyterlab version 3 no longer needs to have extensions installed separately.  Hurrah!  Also the config file with the password is now in `~/.jupyter/jupyter_server_config.py` instead of `~/.jupyter/jupyter_notebook_config.py`.
@github-actions
Copy link

github-actions bot commented Feb 3, 2021

Thank you for your contributions!

A preview of your changes can be viewed at:

@rsignell-usgs
Copy link
Member Author

@clyne would you be willing to review this?

@clyne
Copy link
Contributor

clyne commented Feb 10, 2021

@clyne would you be willing to review this?

Sorry, but I have zero experience with Jupyter Lab in HPC environments. Perhaps @andersy005 would be willing?

@rsignell-usgs
Copy link
Member Author

@choldgraf , perhaps you could review, now that you guys are on the Pangeo project!

@choldgraf
Copy link

@rsignell-usgs I'd be happy to review but to be honest I don't think I am qualified haha. I still haven't used JupyterLab 3 and haven't been very involved in its development 😬 . Though I think that @GeorgianaElena has recently been working on getting JupyterLab 3 to work in the 2i2c hubs, so maybe she can share some things she's learned?

@GeorgianaElena
Copy link

Hi there 👋
The JupyterLab3 for the 2i2c hubs is still a work in progress actually (if you want to follow up with it, it's this one: 2i2c-org/infrastructure#204)

The most important thing that I learned when trying to switch to JupyterLab3 is making sure that all the previous extensions you were using are actually compatible with v3. This means that they should have the jupyterlab extension be installed automatically as part of the python package pip installation.

For example, I noticed jupyter-server-proxy being mentioned here. Making it fully compatible with JupyterLab3 is a work in progress right now jupyterhub/jupyter-server-proxy#233, but shouldn't be long before a new release with this change :D

Hope I've been of any help 🌻

@rsignell-usgs
Copy link
Member Author

Thanks @andersy005 for the fixes, and thanks @choldgraf for passing the buck to @GeorgianaElena ! 😸

@GeorgianaElena , looks like with jupyterhub/jupyter-server-proxy#245 we are good to go with jupyter-server-proxy, right?

rsignell-usgs and others added 3 commits February 18, 2021 15:55
Co-authored-by: Anderson Banihirwe <axbanihirwe@ualr.edu>
Co-authored-by: Anderson Banihirwe <axbanihirwe@ualr.edu>
@rsignell-usgs
Copy link
Member Author

The labextensions seem to be working fine, so merging

@rsignell-usgs rsignell-usgs merged commit 1ea6472 into master Mar 2, 2021
@rsignell-usgs rsignell-usgs deleted the rsignell-usgs-patch-1 branch March 2, 2021 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants