BREAKING CHANGE: env var CONTRACT_LOCATION renamed to CONTRACT_ORIGIN.
CONTRACT_LOCATION environment variable (in the docker-compose file) renamed to CONTRACT_ORIGIN for clarity <-- this change will affect nightfall & other applications using Timber. (They will need to update this variable name in their docker-compose file, if they choose to pull the latest docker image of Timber).
New option added to CONTRACT_ORIGIN: 'compile'. Timber relies on the contract interface json files having been compiled using solc. Some projects (like one I'm currently working on) use a different solidity compiler (e.g. sol-compile), and therefore the contract interface json is completely different. This means Timber can't 'understand' those jsons. Solution: add a 'compile' env var which tells Timber to compile a folder of mounted contracts using solc at start. <-- this change will not affect nightfall or other applications using Timber (because it is an additive feature; the other options haven't been changed).
BREAKING CHANGE: env var CONTRACT_LOCATION renamed to CONTRACT_ORIGIN.
CONTRACT_LOCATION
environment variable (in the docker-compose file) renamed toCONTRACT_ORIGIN
for clarity <-- this change will affect nightfall & other applications using Timber. (They will need to update this variable name in their docker-compose file, if they choose to pull the latest docker image of Timber).New option added to
CONTRACT_ORIGIN
: 'compile'. Timber relies on the contract interface json files having been compiled using solc. Some projects (like one I'm currently working on) use a different solidity compiler (e.g. sol-compile), and therefore the contract interface json is completely different. This means Timber can't 'understand' those jsons. Solution: add a 'compile' env var which tells Timber to compile a folder of mounted contracts using solc atstart
. <-- this change will not affect nightfall or other applications using Timber (because it is an additive feature; the other options haven't been changed).