Teku validator client with separated charon and monitoring #278
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
docker compose --env-file ./.env -f examples/network.yml -f examples/charon.yml -f examples/monitoring.yml -f examples/teku-vc.yml up -d --build
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.
I am using these files to run teku as a distributed validator client on top of the RocketPool smartnode stack
docker compose --env-file ./.env -f examples/rocketpool_net.yml -f examples/charon.yml -f examples/monitoring.yml -f examples/teku-vc.yml up -dI included a network.yml file that creates a 'dvnode' network for a setup where all of the clients would be created by Obol