Kyso's New Jupyterlab Extension
Kyso has recently launched a new Jupyterlab extenstion, which enables users to publish their notebooks to Kyso directly from within Jupyterlab, whether they are actually on Kyso's cluster, using any cloud hosting service such as AWS or GCP, or simply working from their local machine. For information on the extension's prerequisites and installation, take a look at our documentation on Github.
To install the extension, run the following.
For Jupyter Lab 0.35:
jupyter labextension install @kyso/jupyterlab
For Jupyter Lab 0.34:
jupyter labextension install @email@example.com
Note that this install requires node 5 or later. If you encounter any issues such as ValueError: Please install nodejs 5+ and npm before continuing installation when installing the above, run the following & then install the extension:
sudo apt-get install nodejs -y
sudo apt-get install npm -y
Once installed, refresh the page & you will see the Kyso option in the top navbar.
To ensure the most efficient publishing process, only those notebooks and files within the current directory when you hit that Publish button will be attached to the rendered notebook on Kyso's frontend. Think of a Kyso publication as similar to a single folder within a Github repository, with the attached data and files accessible within a hidden file browser.
There are 2 reasons for this:
- Firstly, it ensures quick load times when publishing. If you have everything in the one root directory including, say, your installed dependencies, that may mean publishing a folder easily in excess of 100MB.
- Secondly, this structure encourages only publishing the files and data that are pertinent to the rendered notebook, which also simplifies the reproducibility of your study for other users.
Let's visuialise the directory structure:
We are in Directory 3b above. So when we hit Publish to Kyso, only the notebooks and other files within this directory will be published to Kyso. We will render the notebook that you select to our frontend. If there is any confusion in relation to the above, please don't hesitate to send us your questions to firstname.lastname@example.org.