Skip to main content

jupydrive-s3

Github Actions Status A JupyterLab extension which enables client-side drives access.

Screenshot from 2024-05-06 15-22-59

The drives are used as a filesystem, having support for all basic functionalities (file tree-view, editing contents, copying, renaming, deleting, downloading etc).

The extension was built using the official JavaScript AWS SDK.

Drives Compatibility

Currently, the extension offers support only for S3 drives.

Configuration

Set CORS Rules

As the extension works in the browser, the S3 buckets need to have certain CORS (Cross-Origin-Resource-Sharing) rules set:

  • http://localhost:* needs to be added to the AllowedOrigins section,
  • GET, PUT, DELETE, HEAD need to be added to the AllowedMethods section.

More information about CORS here and the various ways to configure it here.

Set up credentials

User credentials can be set by accessing Settings -> Settings Editor -> Credentials Provider. Users need to offer a bucket name, region, endpoint, access key ID and secret access key, as well as optionally a path to the folder within the bucket that should act as root.

The extension uses jupyter-secrets-manager to deal with the secret input fields.

[!NOTE] The extension uses the Settings Registry to allow users to set their credentials when not in development mode. As a result, secret values may still be accessible to other extensions. Be aware of the associated security risks.

Requirements

  • JupyterLab >= 4.2.5

Install

To install the extension, execute:

pip install jupydrive_s3

Uninstall

To remove the extension, execute:

pip uninstall jupydrive_s3

Contributing

Development install

Note: You will need NodeJS to build the extension package.

The jlpm command is JupyterLab's pinned version of yarn that is installed with JupyterLab. You may use yarn or npm in lieu of jlpm below.

# Clone the repo to your local environment
# Change directory to the jupydrive_s3 directory
# Install package in development mode
pip install -e "."
# Link your development version of the extension with JupyterLab
jupyter labextension develop . --overwrite
# Rebuild extension Typescript source after making changes
jlpm build

You can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.

# Watch the source directory in one terminal, automatically rebuilding when needed
jlpm watch
# Run JupyterLab in another terminal
jupyter lab

With the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).

By default, the jlpm build command generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:

jupyter lab build --minimize=False

Local enviroment variables

For the local development of the extension, enviroment variables are used to define the required bucket name, region and endpoint, as well as the access key id and secret key, with the additional possibility of defining a different root folder.

Rename the .env.example file to .env and update it with the values needed for your local configuration.

Note: Unless configured differently, the S3 bucket endpoint should follow the format: https://s3.<bucket-region>.amazonaws.com.

Development uninstall

pip uninstall jupydrive_s3

In development mode, you will also need to remove the symlink created by jupyter labextension develop command. To find its location, you can run jupyter labextension list to figure out where the labextensions folder is located. Then you can remove the symlink named jupydrive-s3 within that folder.

Testing the extension

Frontend tests

This extension is using Jest for JavaScript code testing.

To execute them, execute:

jlpm
jlpm test

Integration tests

This extension uses Playwright for the integration tests (aka user level tests). More precisely, the JupyterLab helper Galata is used to handle testing the extension in JupyterLab.

More information are provided within the ui-tests README.

Packaging the extension

See RELEASE

Release files for jupydrive-s3 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for jupydrive-s3 0.1.0
File Size Uploaded
jupydrive_s3-0.1.0.tar.gz 299.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for jupydrive-s3 0.1.0
File Interpreter ABI Platform
jupydrive_s3-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 447.2 kB

Release files / jupydrive_s3-0.1.0.tar.gz

Download URL jupydrive_s3-0.1.0.tar.gz
Size 299.0 kB
Tags Source
SHA-256 checksum
How to use checksums
23b18f58120ddd1c2e325adc7524de8bd1c866ca4aa1a7e04ce133ffc75a981e
BLAKE2b-256 checksum
How to use checksums
1b4221e1697fc95038046aacfa4717d654dc45e7441a61d36b7688729e21e001
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.10

Release files / jupydrive_s3-0.1.0-py3-none-any.whl

Download URL jupydrive_s3-0.1.0-py3-none-any.whl
Size 148.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4343e025c8963b349be3198356a6f70ba3b05044eafe64da932ae2d6fa4f0145
BLAKE2b-256 checksum
How to use checksums
621fc4979ffe4085cfa9b4e9d50741039d82d318c33e63c946da5c4041aea9ae
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.10
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page