combine graph-node docker-compose with ganache for local development #60
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
gtaschuk
force-pushed
the
docker-setup
branch
from
bd7588c to
32335d0
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.
I propose using a docker-compose file to start up both graph-node services, and ganache for local development - since graph-node vendors a docker-image, we don't have to clone that repo in order to use it
I used a mnemonic in the docker-compose ganache service declaration (the same one that is in the merkle redeem project) so we can add a subgraph.ganache.yml with consistent contract addresses (since they are deterministically created)