Quickstart

The shortest real path from a fresh checkout to a running enclave that an agent can talk to over its local metadata socket.

View as Markdown Edit on Tangled

Before you start

Daevix is self-hosted and alpha; there is no hosted console. Everything below runs on your own machine. Tooling — Go plus sqlc, goose, golangci-lint, and mkcert — is provisioned by mise; there is no go on your PATH until mise is active.

Build the binary

Provision the toolchain, generate local TLS certificates, and build dvx into bin/. Servers are TLS-only, so the certs come first.

dvx

$ mise install$ make dev-certs$ make build$ ./bin/dvx --version

make test runs the unit tests (go test -short ./...) if you want to confirm the tree before running anything.

Run the IMDS daemon locally

make run-imds runs dvx serve imds in the foreground over TLS. It sets DVX_ENCLAVE_ID=dev-local and serves the IMDS-like metadata socket at /tmp/dvx-imds.sock — the same socket an agent mounts to read its identity.

dvx

$ make run-imds

In a second shell, query the metadata service the way an agent would — over the unix socket, not the network:

dvx

$ curl -s --unix-socket /tmp/dvx-imds.sock http://imds/v1/identity