feat: run devnet with configurable environments #322
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
merklefruit
changed the title
merklefruit
changed the base branch from
unstable
to
lore/feat/holesky-launch
merklefruit
force-pushed
the
nico/feat/consistent-devnet-images
branch
from
44dd267
to
4edfe87
Compare
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 PR tries to address a shortcoming: running the Bolt devnet with all of its components locally can be difficult as we don't have all the components in the same repository.
Right now we require building helix, mev-boost, and builder as external images, and we assume users trying to run the devnet are also doing that themselves.
This is not robust. A better solution is to add a parameter to the
just uprecipe, defaulting to "latest" meaning that the kurtosis devnet will try to use the latest released version of all images and components.Then, we can set it to something like "local" (e.g.
just up local) to specify that we want to use locally-built images tagged with:localinstead of:latest.The next step in terms of UX is to add a simple way to explain what images one needs to build each time, but this will be restricted to devs actively working on those components instead of anyone trying to just get up and running.