Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: run devnet with configurable environments #322

Draft
wants to merge 1 commit into
base: unstable
Choose a base branch
from

Conversation

merklefruit
Copy link
Collaborator

@merklefruit merklefruit commented Oct 25, 2024

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 outside 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 up recipe, 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 :local instead 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.

@merklefruit merklefruit changed the title feat: example devnet config with default tag feat: run devnet with configurable environments Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant