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

Support custom consensus.json files #61

Open
jdtzmn opened this issue Jul 23, 2021 · 0 comments
Open

Support custom consensus.json files #61

jdtzmn opened this issue Jul 23, 2021 · 0 comments

Comments

@jdtzmn
Copy link

jdtzmn commented Jul 23, 2021

Problem

Algod allows for custom consensus.json files as long as they are located in the data directory, but getting a consensus.json file to the data directory requires the copyTo command and several docker up/downs. It would be nice if there was a CLI argument that allowed you to pass your own consensus.json file on ./sandbox up.

Related to #36.

Solution

Add a CLI argument to sandbox for copying a consensus.json file into sandbox.

Stretch goal: read the consensus file and only overwrite/insert consensus config that was changed; don't replace the entire file. This way users could specify "consensus overrides" instead of replacements, and would make the customization more future-proof.

Dependencies

None

Urgency

Not urgent. Would be a nice improvement.

@jdtzmn jdtzmn added the new-feature-request Feature request that needs triage label Jul 23, 2021
@algoanne algoanne added Low Priority and removed new-feature-request Feature request that needs triage labels May 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants