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
Run an EchoVault instance in WASM on the docs site. The goal is to allow the user to run commands in the browser instead of only having hard-coded code examples.
Ideally, we should be able to serve this through GitHub pages. If this proves to be too much of a challenge, we can deploy the docs to an alternative platform.
The text was updated successfully, but these errors were encountered:
So it looks like because we have dependencies (specifically, boltdb/bolt and hashicorp/go-sockaddr) that utilize system calls we can't compile a wasm instance of sugardb. We could set up a sandboxed instance on the backend potentially. This means we either:
Host on something other than github pages.
Set it up as a microservice.
For option 2, I'm not super well versed in security best practices so I'm not sure how secure we can make it so that we aren't exposing endpoints to the client directly. My guess is we'd need a reverse proxy of some kind?
Run an EchoVault instance in WASM on the docs site. The goal is to allow the user to run commands in the browser instead of only having hard-coded code examples.
Ideally, we should be able to serve this through GitHub pages. If this proves to be too much of a challenge, we can deploy the docs to an alternative platform.
The text was updated successfully, but these errors were encountered: