You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
read exported data from Thyra (possible? with password?)
dependencies:
All these features uses the smart contract deployer. in order to do clean stuffs we have to factorize this.
There is already a big part of the work which is already done here: https://github.com/massalabs/massa-sc-utils
We should use it, and adapt for our needs. This should also be nice to add a command line feature for these tools
(i.e npx massa-utils deploy mycontract.wasm") to be use in npm script "deploy": "massa-utils deploy"
We need to clarify the difference between deploying a SC directly and deploying a SC through a deployment contract.
It will be good to decide of an appropriate wording about this
brainstorming option names for the 'deploy through a deployer smarcontract' use case:
--generate-deployer
--deploy-function
--createSC
I propose to generalize the use of typescript. (vanilla javascript forbidden) @massalabs/massa-sc-utils is already a typescript module
The text was updated successfully, but these errors were encountered:
Need:
Two new commands
Set en DNS entry:
examples:
npx @massalabs/sc-toolkit dns --set toto.massa
optionnal flags:
--rpc
--dnsAddress
--privateKey (?)
Deploy website:
examples:
npx @massalabs/sc-toolkit deployWebsite mywebsite.zip
optionnal flags:
--rpc
--dnsAddress
--privateKey (?)
For private key, several possibilities:
dependencies:
All these features uses the smart contract deployer. in order to do clean stuffs we have to factorize this.
There is already a big part of the work which is already done here: https://github.com/massalabs/massa-sc-utils
We should use it, and adapt for our needs. This should also be nice to add a command line feature for these tools
(i.e npx massa-utils deploy mycontract.wasm") to be use in npm script
"deploy": "massa-utils deploy"
We need to clarify the difference between deploying a SC directly and deploying a SC through a deployment contract.
It will be good to decide of an appropriate wording about this
brainstorming option names for the 'deploy through a deployer smarcontract' use case:
--generate-deployer
--deploy-function
--createSC
I propose to generalize the use of typescript. (vanilla javascript forbidden) @massalabs/massa-sc-utils is already a typescript module
The text was updated successfully, but these errors were encountered: