Skip to content

Wagi Runtime for WebAssembly
Compare
Choose a tag to compare
@technosophos technosophos released this 08 Jul 19:42
· 119 commits to main since this release
v0.2.0
4711a3a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

This release is the first binary release of Wagi.

Installing

The binary releases for Wagi are located at the bottom of this page. For installation instructions, see the installation guide

All checksums were generated on macOS with the command shasum *.tar.gz

ad4114b2ed9e510a8c24348d5ea544da55c685f5  wagi-v0.2.0-linux-amd64.tar.gz
463a60c5056b20eb8c82263560e05261e360e1d1  wagi-v0.2.0-macos-amd64.tar.gz
c8711f2c9464f6acc8a2175b2c0c219f0dee3ef2  wagi-v0.2.0-windows-amd64.tar.gz

Using as a Crate

This release does not support crate-based usage of Wagi.

Caveats

Wagi is considered pre-production, and should not be used in a production environment. Likewise, APIs, file formats, and protocols are subject to change between now and 1.0.0-beta.1.

Major Features

  • CGI/1.1 support
  • Bindle support
  • OCI registry support
  • Custom environment variables and hostname
  • Wasm caching

Bug Fixes

Bug fixes are not reported for this first version

Known Issues/Missing Features

  • The binary client may report itself to be 0.1.0
  • There is a known but un-diagnosed issue in which starting many Wagi instances on Windows can cause some instances to hang, contending for a port.

Breaking Changes

  • Many features from the unreleased 0.1.0, including virtual hosting, were removed or refactored out
  • modules.toml is different from the unreleased 0.1.0 version
  • Environment variables can no longer be specified in modules.toml

What's Next?

Wagi is rapidly evolving. Our next milestone is for cleanup and bugfixing.

Assets 5