Skip to main content

An extension to encrypt and upload the working directory to EscrowAI

Project description

escrowai_jupyter

Github Actions Status An extension to encrypt and upload the working directory to EscrowAI

Requirements

  • JupyterLab >= 4.0.0

Install

To install the extension, execute:

pip install escrowai_jupyter

Uninstall

To remove the extension, execute:

pip uninstall escrowai_jupyter

Usage

To use the package, the following prerequisites must be met:

  1. Working directory must be the algorithm to be uploaded to EscrowAI.
cd {algorithm_directory}
  1. Variables CONTENT_ENCRYPTION_KEY and PROJECT_PRIVATE_KEY must be present in the environment and base64 encoded. The CEK must match an uploaded WCEK on the given project, and the Project Private Key must be an RSA-4096 private key matching a Project Public Access Key on the given project.

  2. A config.yaml file must be present in the working directory, with the following format:

BEEKEEPER_USERNAME: username
BEEKEEPER_PROJECT_ID: project_id
BEEKEEPER_ORGANIZATION_ID: organization_id
BEEKEEPER_ENVIRONMENT: dev | tst | stg | prod (default = prod)
ALGORITHM_TYPE: validation | training (default = validation)
ALGORITHM_NAME: name (default = Jupyter Algorithm)
ALGORITHM_DESCRIPTION: description (default = null)
VERSION_DESCRIPTION: version_description (default = null)
ENTRYPOINT: algorithm_executable (default = run.py)

Once prerequisites are met, open the JupyterLab command pallete and select "Upload to EscrowAI". The algorithm directory will then be automatically encrypted and uploaded to EscrowAI.

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 escrowai_jupyter 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

Development uninstall

pip uninstall escrowai_jupyter

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 escrowai-jupyter within that folder.

Packaging the extension

See RELEASE

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

escrowai_jupyter-1.0.1-py3-none-any.whl (29.8 kB view details)

Uploaded Python 3

File details

Details for the file escrowai_jupyter-1.0.1-py3-none-any.whl.

File metadata

File hashes

Hashes for escrowai_jupyter-1.0.1-py3-none-any.whl
Algorithm Hash digest
SHA256 86e428719d729237baaa82df3ee978f9566d98c9c9a3f5d991fe3e4ef5dffe8c
MD5 c7cc227e9e0f42344b7db4485253e921
BLAKE2b-256 20d2cc7a60b02b0056ecd80b20b2e834b2d473f5f7bbbc7ed0fb98b3ba8776bd

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page