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
People uses a lot this method, and is one of the main commands we will need for removing the current near-cli-js from all our tutorials.
Either we implement this, or:
Come up with a new flow explaining people how to create dev accounts
Completely ditch dev account (an idea really to consider, since people get confused about the dev accounts a lot)
While writing this, I am feeling maybe we should just do (2) instead of implementing the dev-deploy, but would like to hear opinions from the devs of this tool.
The text was updated successfully, but these errors were encountered:
@gagdiez I believe that dev-deploy is responsible for the developers drop off as with this magic you don't know how to have a normal account id, how to deploy to mainnet, etc.
cargo-near has two methods instead:
cargo near create-dev-account
and then
cargo near deploy
Would you like to give it a try and see if that helps?
People uses a lot this method, and is one of the main commands we will need for removing the current
near-cli-js
from all our tutorials.Either we implement this, or:
dev
accountsdev
account (an idea really to consider, since people get confused about thedev
accounts a lot)While writing this, I am feeling maybe we should just do (2) instead of implementing the
dev-deploy
, but would like to hear opinions from the devs of this tool.The text was updated successfully, but these errors were encountered: