Easier WASI setup

[ethanfrey]

Builds on #26 but moves the setup and build instructions into easy scripts. Also assert the MSRV there, as a fellow (frontend) dev hit odd issues with a very old Rust version.

Setup seems to work.

The build script fails due to some issue in the code configuration I think. That is ./scripts/build_wasi.sh as well as cd wasi/square/ && cargo component build --release provides:

error: component registry package `lay3r:avs` (v`0.3.0`) has digest `sha256:891753e8eab23c067ef8095359c28e4296a65faf416103e797f468dcb5f6b4a5` but the lock file specifies digest `sha256:5ca2842d9fbc411429870dfe3b69cb6f787f7cea30598518849cf2edf03c7ce2`

[calvinrp]

Builds on #26 but moves the setup and build instructions into easy scripts. Also assert the MSRV there, as a fellow (frontend) dev hit odd issues with a very old Rust version.

Setup seems to work.

The build script fails due to some issue in the code configuration I think. That is ./scripts/build_wasi.sh as well as cd wasi/square/ && cargo component build --release provides:

error: component registry package `lay3r:avs` (v`0.3.0`) has digest `sha256:891753e8eab23c067ef8095359c28e4296a65faf416103e797f468dcb5f6b4a5` but the lock file specifies digest `sha256:5ca2842d9fbc411429870dfe3b69cb6f787f7cea30598518849cf2edf03c7ce2`

Investigating. I was switching my local config between test and prod registry that had different SHAs.

[ethanfrey]

Make sense. Can you also add docs on how to pull from a registry (and push there)? Maybe pushing elsewhere, in internal docs, but at least getting latest from registry here

[calvinrp]

Make sense. Can you also add docs on how to pull from a registry (and push there)? Maybe pushing elsewhere, in internal docs, but at least getting latest from registry here

Will do today. The registry config for a project should really be committed to the workspace in the repo, instead of global config. It was there in cargo-component but got refactored in the switch to support both Warg and OCI registries. Likely I could get this fixed in the next release of cargo-component (this week I think).

It would drastically simplify the setup instructions for the hackathon devs.

[calvinrp]

I forgot that cargo-component has a cache dir in addition to wkg and warg. Created an issue to make it easier to clear that cache, at the very least.

This is an unlikely edge case for the hackathon. Only would occur if you are switching around registry config in weird ways, like I was.

[calvinrp]

When the simpler setup is available, we can revise with a follow up PR.