Dev chain fast #208
Merged
Dev chain fast #208
Conversation
This file contains hidden or 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
… besides the existing config that indexes the old sidechain. The deploycontainer for the fastchain will start up that new graph node config
harbu
approved these changes
Aug 9, 2023
jtakalai
approved these changes
Aug 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
added subgraph-deploy-container, graph-node config, and fastchain containers in a non-breaking way, now the old setup with the sidechain can be started Or alternatively the new fastchain can be started.
Both work on the same docker-compose and there is no need to edit anything.
The existing integrationtests should not be affected by this at all.
Only thing that might break is starting EVERYTHING from the docker-compose, then one of the two graph-node configs will probably not work