embarklabs/embark
2
0
Fork 0
mirror of https://github.com/embarklabs/embark.git synced 2025-02-08 11:54:24 +00:00
Code Issues Projects Releases Wiki Activity

feat(@embark/site): add documentation on minimalContractSize

Browse Source
This commit is contained in:
Jonathan Rainville 2019-07-11 16:15:04 -04:00
parent b0cccaea05
commit f9fb302740
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
site/source/docs/contracts_configuration.md
View File

@ -347,6 +347,17 @@ tracking: 'path/to/some/file'
Having the file referenced above under version control ensures that other users of our project don't redeploy the Smart Contracts on different platforms. Having the file referenced above under version control ensures that other users of our project don't redeploy the Smart Contracts on different platforms.
### Reducing contract size
To reduce the size of the contract JSON files that are included in the build directory, you can set `minimalContractSize` to `true`. It defaults to `false`.
When set to `true`, Embark will not put te bytecode, gas estimates and other big configurations in the JSON file.
```
minimalContractSize: true
```
## Deployment hooks ## Deployment hooks
Sometimes we want to execute certain logic when Smart Contracts are being deployed or after all of them have been deployed. In other cases, we'd even like to control whether a Smart Contract should be deployed in the first place. For those scenarios, Embark lets us define the deployment hooks `beforeDeploy`, `deployIf`, `onDeploy` and `afterDeploy`. Sometimes we want to execute certain logic when Smart Contracts are being deployed or after all of them have been deployed. In other cases, we'd even like to control whether a Smart Contract should be deployed in the first place. For those scenarios, Embark lets us define the deployment hooks `beforeDeploy`, `deployIf`, `onDeploy` and `afterDeploy`.