ObolNetwork / ObolNetwork/charon-distributed-validator-node
Create a run.sh for commit-boost
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 91
- Forks
- 235
- Avg merge
- 1h 42m
- Merged PRs (30d)
- 1
Description
🎯 Problem to be solved
In all other VCs etc, we override the docker cmd with a script, that parses the .env vars and passes them to the real runtime command. This allows us to prep config or keys, or other things.
For commit-boost, we have to copy a command manually.
We can skip this user friction by writing a script that prepares the right config.yaml. we could also make it work with .env vars and selective volume mounts. (ie. mount "./commit-boost/config.sample.${NETWORK:-mainnet}.toml:/correct_mount_path/config.toml" if that is tested and works).
🧪 Tests
- Works in local docker-compose
- Has a attested on a testnet at least once
👐 Additional acceptance criteria
❌ Out of Scope
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the local docker-compose configuration and the existing commit-boost command, then trace how .env values and the network-specific config sample are currently supplied. Done means a run.sh prepares config.yaml, supports the described environment and volume behavior where tested, works in local docker-compose, and has been attested on a testnet.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, shell
- Domain
- blockchain, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100