Publish and run Registry packages
Connect Wasmd to the current Workers-based Wasm Native Registry.
Connect your Registry
Unqualified packages use hub.wasmd.com. Login validates your token and stores credentials without changing the default registry. For another registry, use a host-prefixed package or --registry URL on pull, run, and push. Set WASMD_REGISTRY_TOKEN before running this PowerShell example.
$env:WASMD_REGISTRY_TOKEN | wasmd login --token-stdinPublish an immutable version
Replace demo with a namespace you own. A push includes the artifact and can publish its repository README as the package Overview. --readme selects a UTF-8 file up to 64 KiB; --no-readme preserves the existing Overview.
wasmd push hello.wasm demo/hello:1.0.0 --license Apache-2.0
wasmd pull demo/hello:1.0.0
wasmd run demo/hello:1.0.0Verify and reuse artifacts
pull and run share the SHA-256 image cache under ~/.wasmd/images. Downloads are checked against both manifest digest and byte length. Existing files are verified before reuse; corrupted cache entries are downloaded again. --force forces a new download. WASMD_CONFIG overrides the configuration root.
Self-host the current Registry
The current Registry runs on Cloudflare Workers with D1 for accounts and metadata and private R2 for artifacts. It supports email/password and GitHub accounts, namespace ownership, scoped tokens, package search, immutable releases, yank/unyank, and Component/WIT inspection. Use the Registry repository deployment guide for provisioning and migrations. Earlier registry.wasm service examples are not deployment instructions for this implementation.
Based on the current repository documentation. Check your installed version and the linked acceptance records when adopting development features.
Read the Wasmd source document ↗Registry deployment guide ↗