Closed frol closed 11 months ago
cargo near deploy should do the following:
cargo near deploy
cargo near build
near-cli-rs
near contract deploy my-new-dev-account.testnet use-file ./target/near/adder.wasm ...
So the final command could look like:
cargo near deploy \ frol.near \ with-init-call \ new \ json-args '{"param1": 1}' \ prepaid-gas '100.000 TeraGas' \ attached-deposit '0 NEAR' \ network-config testnet \ sign-with-...
cargo near deploy \ frol.near \ without-init-call \ network-config testnet \ sign-with-...
Note: We don't want to implement dev-deploy magic in cargo-near, instead, I suggest to introduce cargo near create-dev-account #106
dev-deploy
cargo near create-dev-account
Note: All the features available in near-cli-rs for deployment should be inherited here, so near-cli-rs should be reused here.
cargo near deploy
should do the following:cargo near build
code internallynear-cli-rs
code in such a way that interactive part picks up fromnear contract deploy my-new-dev-account.testnet use-file ./target/near/adder.wasm ...
So the final command could look like:
Note: We don't want to implement
dev-deploy
magic in cargo-near, instead, I suggest to introducecargo near create-dev-account
#106Note: All the features available in near-cli-rs for deployment should be inherited here, so near-cli-rs should be reused here.