exo init
#407
Merged
exo init
#407
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
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.
This introduces an early version of an
exo initcommand. It does whatexo workspace init, but also will apply a manifest. It's intended to be used interactively, and so could someday include project templating flows and the like.I made this now because I'm trying to write better "Getting Started" docs, and realized we needed a better getting started experience :)
The intention is that
exo runis a great way to get started forforemananddocker-compose upusers, butexo initis an easier way to get started with the GUI.Just going to get to main, but happy to accept post-hoc reviews.