You can specify for each contract and environment its gas costs (in wei) and
If you prefer it’s also possible to specify the contract arguments by their variable name instead of a list:
If you are using multiple contracts, you can pass a reference to another contract as
$ContractName, Embark will automatically replace this with the correct address for the contract.
You can also specify interfaces and choose to not deploy contracts (for e.g in case they are interfaces)
You can deploy many instances of the same contract. e.g
You can specify which Account you want to deploy a contract from. This can be specified using “from” or “fromIndex” parameters.
| “from” - should be account address string.
| “fromIndex” - should be index in accounts array as retrieved by web3.eth.getAccounts() .
If both “from” and “fromIndex” are specified, the “from” will be used.
Contracts addresses can be defined, If an address is defined the contract wouldn’t be deployed but its defined address will be used instead.
You can specify actions to do after the deployment of a contract using the “onDeploy” parameter.
You can specify actions to do after ALL contracts have been deployed by using the “afterDeploy” parameter.
By default embark will look for the contracts inside the folder defined in “contracts”` property in embark.json.
However it’s possible to specify the contract filepath:
You can even specify files on Git, Github or over HTTP(S):
It’s also possible to specify a contract file from a npm package:
If using solidity it’s also possible to directly import contract files inside the dapp from folders that are not explicity defined in the “contracts” propery of embark.json.
You can also import a contract file from a npm package:
You can even use files directly from Git, Github or directly from HTTP(S):