@leverj/chain-deployment

Chain Deployment

configure the deployed project/package with the minimal configuration looking like here.
create a .env file in the deployed project/package root, overriding config values like here.
create an AUTH_DIR to contain per-NODE_ENV (i.e. test, ..., livenet) directories
for each NODE_ENV create a secrets.json file in the respective directory, containing config values like here
create a deploy script similar to this, to be executed via:
```
$> NODE_ENV=<env> yarn deploy
```
the resulting deployment artifacts will reside under the configured<deploymentDir>/ directory

to support interaction with deployed contract, you can generate a correponding source files like so:

create a generate-contract-exports script such as this, to be executed via:
```
  $> yarn generate-contract-exports
```
the resulting javascript files will reside under the <deployed-project-root>/src/contracts/ directory