🎯 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
👐 Additional acceptance criteria
❌ Out of Scope
🎯 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
👐 Additional acceptance criteria
❌ Out of Scope