Is your feature request related to a problem? Please describe.
For non-NEAR natives, creating an account's a slight entry barrier. It would be helpful if we ran a near-cli-rs docker container to near create-account on testnet as a oneshot command and put it in the readme. This could output the keypair in stdout.
Describe the solution you'd like
It might also be helpful to bootstrap the http-config file with the info returned automatically so we can use the scripts/enrich.sh to populate the config (same as CI)
HTTP_API_TEST_SECRET_KEY=YOUR_SECRET_KEY(is the "private_key" field) \
HTTP_API_TEST_ACCOUNT_ID=YOUR_ACCOUNT_ID \
HTTP_API_TEST_NAMESPACE=null
scripts/enrich.sh
They can also select CONTRACT_ID or just update the config file afterward.
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe.
For non-NEAR natives, creating an account's a slight entry barrier. It would be helpful if we ran a
near-cli-rsdocker container tonear create-accounton testnet as a oneshot command and put it in the readme. This could output the keypair in stdout.Describe the solution you'd like
It might also be helpful to bootstrap the http-config file with the info returned automatically so we can use the
scripts/enrich.shto populate the config (same as CI)They can also select CONTRACT_ID or just update the config file afterward.
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.