[draft] initial idea for how to structure ephemeral deployment moons #3315
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
arthyn
approved these changes
Mar 8, 2024
There was a problem hiding this comment.
I think this generally makes sense. @Fang- reading this https://github.com/urbit/tools/wiki/conn.c-Usage-Guide it seems like the thread needs to be inlined and stripped of some of the opening imports and stuff since that's included in khan-eval right?
|
going to just push this through and we can make another PR with actual deploys |
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.
Just trying to structure out how we could potentially start up ephemeral moons for development branches.
To make this work we need a hoon thread to run through click to generate a moon. We then need to write that output to a file, then extract the moon name and key, and then use that to boot the one-off moon. One problem I see with the current approach is that the bash script copied/ran on the VM host is very much a "one shot" type thing where the script is just ran one time, similar to how our current
deploy.shscript is ran. Need to determine how we can actually see if the moon is successfully booted before moving forward with the deployment script itself.