authzed / playground Goto Github PK

authzed/actions has some utilities for publishing to all of our registry targets that we should be using (docker hub gets most of our traffic)

Precondition: Playground Docker image build from main branch, tagged spicedb-playground:master

1. run container via docker run -it -p 3000:3000 spicedb-playground:master
2. load <host>:3000 in browser FF (based on 115.6.0esr) or Edge (123.0.2420.81)

Expected: Playground environment with validation support
Observed: Playground environment with non-working validation support and error "Could not start the Development System. Please make sure you have WebAssembly enabled."

The feature works on https://play.authzed.com/schema, meaning the browsers apparently support the required features

Despite having a max-age header, the wasm bundles are given a random query parameter that busts the cache each load.

I think the intention was originally to have this parameter be a SHA of the contents of the bundle.

Attempting to run the official Docker image (sha256:6d0bea9c40d8e5837a7c2e907045341d7be13be8101801661e03f558c7c3a878) as described in the README fails with

docker run -it -p 3001:3000 ghcr.io/authzed/spicedb-playground:latest
WARNING: The requested image's platform (linux/arm64/v8) does not match the detected host platform (linux/amd64/v4) and no specific platform was requested
exec ./docker-entrypoint-wrapper.sh: exec format error

An image build from the main branch (ref 769c8ec) works, this might just be about publishing a new Docker image.

Add a guide for including custom schema and test relationships and make them available in the example drop down menu.