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

update generated config with additional comments #382

Merged
merged 6 commits into from
Oct 23, 2023

Conversation

ryanwaits
Copy link
Contributor

Description

update comments in the generated Chainhook.toml file around the stacks_node_rpc_url and bitcoind_zmq_url to add a bit more clarity around what they are and when to use one over the other.

Checklist

  • All tests pass
  • Tests added in this PR (if applicable)

# Chainhook must be able to receive Bitcoin block events.
# These events can originate from either a Stacks node or a Bitcoin node's ZeroMQ interface.

# By default, the service is set to receive Bitcoin block events from the Stacks node (via burnchain):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"via burnchain" might beg some context... Burnchain is a deprecated PoX v1 term that persists in old Stacks Node software. Not even some (a lot of?) Stacks users might know what it is. Is there a better way to put it?

@mefrem
Copy link
Contributor

mefrem commented Aug 11, 2023

Made a comment, otherwise looks great! This is exactly what @MicaiahReid thought would make the docs stronger is providing more context to developers about "what is needed and when".

@@ -36,6 +39,9 @@ max_number_of_processing_threads = 16
max_number_of_networking_threads = 16
max_caching_memory_size_mb = 32000

# If you don't require historical data for your predicates or wish to avoid downloading
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The TSV file is not downloaded every time. It is downloaded once, and future runs use that cached version until a new one is available.

@smcclellan smcclellan requested a review from MicaiahReid August 14, 2023 17:07
Added @MicaiahReid's suggestions.
Co-authored-by: Micaiah Reid <micaiahreid@gmail.com>
Copy link
Contributor

@lgalabru lgalabru left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @ryanwaits!

@lgalabru lgalabru merged commit 343f55d into develop Oct 23, 2023
@lgalabru lgalabru deleted the improvement/cli-config-generator branch October 23, 2023 15:12
@lgalabru lgalabru had a problem deploying to Development-mainnet October 23, 2023 15:51 — with GitHub Actions Failure
@lgalabru lgalabru had a problem deploying to Development-testnet October 23, 2023 15:51 — with GitHub Actions Failure
Copy link

🎉 This PR is included in version 1.2.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants