zero-install / cloud-IDE option for getting started with agoric-sdk

[dckc]

I just got it working on gitpod. Details to follow.

https://github.com/dckc/agoric-gitpod-nix

cc @michaelfig @katelynsills @rowgraus

[katelynsills]

Cool! What would this mean, exactly? Would it be for smart contract development or dapp development?

[dckc]

Either one, IIUC.

It means someone could follow a link to a web site that acts just like vs-code, with agorc-sdk, yarn, node, and go already installed and ready so that yarn test works. agoric init demo should work too.

I think I tested agoric start with the wallet and fake chain and all that.

[katelynsills]

Ooo that sounds great!

[dckc]

connecting to the wallet doesn't seem to quite work...

2021-09-16T02:28:02.880Z web: 127.0.0.1:37292: Invalid origin host https://8000-purple-clam-arf9beuf.ws-us15.gitpod.io is not localhost

[dckc]

Here's a 20 minute live-coding session that shows me getting as far as the wallet connecting problem above:

• agoric-sdk on Gitpod: zero-install BLD tools (WIP)

ew... the video quality is horrible. I must have told OBS to use low resolution or something.

[dckc]

Yes! #3838 gets us past the localhost issue:

[dckc]

I'm not the only one having this funky terminal font issue. This settings tweak works for me just now:

"terminal.integrated.gpuAcceleration": "canvas"

[dckc]

@michaelfig with the wallet running in some gitpod origin, how do I tell a dapp such as the fungible faucet demo to talk to it?

[michaelfig]

That's a yet-to-be-solved problem for browsers like Brave that aggressively block iframe service workers, cookies, and local storage, but with Chrome or Firefox, you can navigate your browser to https://local.agoric.com and fill out the form to point to your wallet with gitpod origin.

[samsiegart]

The wallet connection works for me with the local.agoric.com method above, but the faucet doesn't connect to the API server:

WebSocket connection to 'ws://127.0.0.1:8000/api/fungible-faucet' failed

We need to somehow dynamically change the hardcoded origin to use the gitpod one.

[dckc]

One of the big challenges in this area is that we don't support the npm install -g agoric convention because things move too quickly for that to be cost-effective: it would only install the version most recently published to npm, which is rarely what we (the Agoric dev team) want. This is a known issue: #3857

[dckc]

another option to look into: https://stackblitz.com/

[dckc]

related work:
https://mobile.twitter.com/adamleetucker17/status/1513631602269724675
https://marketplace.digitalocean.com/apps/osmosis

[Tyrosine22]

I'm confused. Why is this item in the Doc board? It doesn't seem doc-related.

[dckc]

It's related to getting started. As you're discovering, I have used this issues list for all sorts of devrel stuff. Seems like it's time to be a little more consistent about scope. This sort of stuff can/should move to an agoric-sdk discussion. (I'm on a small screen just now but I can get to it in due course.)