docs: add Nebi in JupyterLab workflows page - #204
Draft
aktech wants to merge 3 commits into
Draft
Conversation
Covers the developer-facing Nebi workflows: creating and using local workspaces, opening notebooks against a workspace's kernel, sharing and pulling published workspaces, diffing versions, cleaning up installed environments, using a workspace for a deployed jhub-apps app, and the two places to reach the Nebi web UI (in-pod launcher tile and the hub-level pinned service card).
Contributor
|
Docs preview for |
… pipeline Plans a Playwright-driven pipeline that captures real screenshots and one handoff video for the workflows in nebi-in-jupyterlab.md, running a local nebi server plus two JupyterLab containers instead of a full cluster.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a page covering the Nebi CLI and web UI workflows a developer runs from inside JupyterLab: local workspaces, opening notebooks against a workspace kernel, sharing/pulling published workspaces, diffing versions, cleanup, using a workspace for a deployed jhub-apps app, and the two Nebi web UI entry points.