Coda Node Startup Script

Can we agree to create a Node Startup Script for every week?

I feel like we are getting lost in the weeds in terms what needs to be run every week.

I personally am spending too much time trouble shooting for what is going wrong every week.

Script:
start_coda.sh

Contents:
coda daemon -background -tracing -no-bans -log-json -log-level Trace -client-port 8301 -external-port 8302 -config-directory /root/.coda-config -external-ip 47.74.66.67 -rest-port 8304 -peer 13.56.250.68:8303 -peer 34.221.177.69:8303 -peer 34.220.216.179:8303 -peer 54.201.212.16:8303 -peer 18.212.75.13:8303 -propose-key /root/coda/keys/proposer -unsafe-track-propose-key

2 Likes

Do you find that all of these arguments are necessary when you run the daemon? Iā€™d love if we could provide good enough defaults to not need a script like this.

For instance, the combination of -background -log-json -log-level Trace should be able to be replaced with just -background now (it automatically logs at a trace level in coda.log). There are default values for all 3 ports and the config directory, so probably not everyone will want to change those.

Maybe I misunderstood the question so feel free to clear it up, definitely want to make sure we keep the cli usable!

1 Like

Agree to most of your suggestions @Schmavery

I would like to suggest further to reduce running the script to just coda (if and where possible)