Skip to main content

Toolchain

The Brewfile installs Go, just, buf, golangci-lint, jq, the RustFS rc client and Lima:
You also need:
  • Docker. The recipes use its default context for Compose and image builds.
  • Node.js 22 or later and pnpm, for the UI and the docs.
  • sqlc, for just sqlc.
  • protoc-gen-go and protoc-gen-connect-go on your PATH, for just proto. buf.gen.yaml runs them as local plugins.
Running hosts needs an Apple silicon Mac with an M3 or later and macOS 15 or later. See the Quickstart for why.

Repository layout

The repository has three Go modules: the root, examples/embed/go and runtimes/go. Recipes that run per module set GOWORK=off.

How the pieces run in development

just dev runs everything at once. Each piece also has its own recipe: just host cross-compiles the host and supervisor into bin/linux-arm64/ first, then stops any running hosts and starts count new ones (1 by default) with memory MiB each (512). warm is how long an instance is kept for reuse (5m, and 0s always cold boots) and prewarm how many to keep booted per function (0). just dev passes the same arguments after its mode and defaults to 3 hosts. The hosts reach Compose at host.lima.internal. just server points at the Compose services by default, and every variable can be overridden from the environment or a .env file. Its mode turns auth on: zitadel or keycloak after just infra zitadel or just infra keycloak, or proxy. See Authentication. just status shows the VM, the running hosts and the number of microVMs.

The local registry for runtimes

just images builds every runtime and pushes it to the Compose registry as localhost:5001/galaxy-io/alchemy/runtime/<tag>. Hosts in the VM pull the same images from 192.168.5.2:5001, the Mac’s address on the Lima network, which needs no TLS. just server sets RUNTIME_IMAGE_PREFIX to 192.168.5.2:5001/galaxy-io/alchemy/runtime, so a function created from source lands on the local build. Run just images again after changing anything under runtimes/.
just server falls back to a fixed ENCRYPTION_KEY so the secrets API works out of the box. It is a published development key. Never reuse it outside local development.

Recipes

just with no arguments lists every recipe.

Building the UI in

The server serves the web UI from ui.Handler(). Built with -tags embedui, it embeds ui/build and serves the app. Without the tag it serves a placeholder page, so go build ./... needs no Node toolchain. just binaries and the release images build the server with the tag:
In development the UI runs from Vite instead. Set API_PROXY_TARGET to proxy it to a server other than http://localhost:8780.