Document how to restart the `~/startup2.sh` when the config.ini is updated.
tpmccallum opened this issue · 2 comments
If a new static ABI is added to the config.ini, the ~/startup2.sh will need to re-run the harvester so that the new ABI can be read into the program and threaded accordingly.
There must be a process for this from a system PID perspective as well as documentation on how to do this.
We will also need to facilitate, the removal of a contract if an ABI is removed from the config.ini
We could/should read the config.ini into the "all" index. If a user removes an ABI from the config.ini then we provide a way to delete that from the "all" index as well. This will be more efficient than making the system reindex because of a change.
The ABI and Bytecode will be uploaded via a user interface in the near future. There are no ABIs in the config anymore.