Add end-to-end app deployment flow with Livebook Teams #2602
Conversation
This file contains 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
|
Uffizzi Preview |
josevalim
approved these changes
May 13, 2024
|
Amazing, thanks for carrying it through the finish line! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When the user clicks "Deployment with Livebook Teams" and there are no organizations, we tell then to create one:
Then, below is the full flow of deploying a new notebook: (1) selecting the workspace; (2) configuring the slug; (3) creating deployment group; (4) starting agent instance; (5) hitting deploy.
deploy-flow-no-deployment-groups.mp4
Finally, below is the flow of deploying another notebook. In this one, the user selects an existing deployment group and is optionally told to set up an app server, if none is up.
deploy-flow-existing-deployment-groups.mp4