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
{{ message }}
This repository has been archived by the owner on Jun 23, 2020. It is now read-only.
NEARStudio should support being pointed to a different AlphaNet or DevNet by either:
Change in a config file;
UI element in the studio itself that allows connecting to a different *Net.
Currently, in order to run NEARStudio on the top of AlphaNet or a different DevNet we need to go through a multistep hacky process.
Suppose we have AlphaNet/DevNet running on 34.208.224.21:3030 and we want to run studio locally on the laptop.
Make sure that alice.near is in the initial authorities of the chain spec used by AlphaNet or DevNet;
Start near studio. Open "Hello World Example" template and modify doInitContract() function, to assign node URL
// Getting config from cookies that are provided by the NEAR Studio.
const config = await nearlib.dev.getConfig();
config.nodeUrl = "http://34.208.224.21:3030";
config.baseUrl = "http://127.0.0.1:3031";
const options = {};
options.nodeUrl = "http://34.208.224.21:3030";
options.baseUrl = "http://127.0.0.1:3031";
// Initializing connection to the NEAR DevNet.
window.near = await nearlib.dev.connect(options);
Save and press "Run"
The text was updated successfully, but these errors were encountered:
NEARStudio should support being pointed to a different AlphaNet or DevNet by either:
Currently, in order to run NEARStudio on the top of AlphaNet or a different DevNet we need to go through a multistep hacky process.
Suppose we have AlphaNet/DevNet running on
34.208.224.21:3030
and we want to run studio locally on the laptop.alice.near
is in the initial authorities of the chain spec used by AlphaNet or DevNet;app.js
local node connection to point to the AlphaNet/DevNet:3031
:config.json
:doInitContract()
function, to assign node URLThe text was updated successfully, but these errors were encountered: