Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nx1cloud.com/llms.txt

Use this file to discover all available pages before exploring further.

The NexusOne Notebook feature provides an interface for browsing JupyterHub notebook files and attaching them to an app version.

​
Why NexusOne attaches notebooks to an app version

NexusOne attaches Notebooks to an app version because of the following reasons:
  • Asset packaging: The notebook becomes part of the app’s bundle, now all related pipeline assets stay grouped together.
  • Deployment consistency: The notebook can reference the same app secrets and inherit IAM roles.
  • Governance: NexusOne manages access through the app’s IAM roles and permissions instead of managing the notebook access separately.
  • Reproducibility: Anyone using the app version gets the exact notebook that matches the pipeline components used at that time.
  • Version control: The notebook becomes part of a specific app version, so NexusOne tracks changes to code logic in the notebook file, alongside DAGs and artifacts.

​
Ways to upload notebooks

You can make a notebook file available in the Notebook UI and attach it to an app version in either of the following ways:
  • Upload the notebook through the Notebook feature.
  • Use s3Cli from the JupyterHub Notebook command-line environment to upload the notebook file.

​
Supported apps you can attach

NexusOne supports several app types in its App Manager feature. You can only attach the following app types to a Notebook:
  • Full pipeline
  • Notebook pipeline

​
Use cases

These examples show how different industries and teams can use NexusOne’s Notebooks capabilities:
  • Financial services: Develop and version data processing logic in a notebook for trading and reporting pipelines, with its changes tracked as part of app versions.
  • Healthcare: Build and validate clinical data workflows in notebooks before adding them to pipeline assets.