Add tooling grammar and ability to spin up an esplora instance on existing bitcoind in doppler file #104
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
Closed
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 turned into a much more difficult feat than I originally had hoped due to permissions issues and how much the run.sh script in the blockstream esplora docker image depended upon making it's own bitcoind instance. However, I was able to get this setup such that a user can now easily point an esplora instance at a bitcoind node running in their doppler cluster. This does not support having multiple esplora instance pointed at the same bitcoind node, but that feels like an anti-pattern and am fine keeping that constraint. Some notes were also added into how to access the esplora instance once it is up as well.
