WASM resource packs

The host runs WASM resources. Every resource is an independent package, so you can combine them by server role.

1. Independent resource packs

Resource packs contain only prebuilt .wasm, resource metadata and documentation — no source code.

2. Server role combinations

3. Install

Download the required .tgz files from the downloads page, put them in the deployment directory (or use a relative path), and run inside that directory:

wasmx add ./keragi-resx.tgz
wasmx add ./keragi-msgx.tgz
wasmx add ./keragi-userx.tgz
wasmx add ./keragi-conn.tgz
wasmx add ./keragi-agix.tgz

Install only what you need. add will:

1. Install the resource pack from the local .tgz;
2. Copy the .wasm files into the deployment’s wasm/;
3. Merge the resource entries into wasmx.json under resources.

Or use a preset (--offline points to the directory containing the .tgz files):

wasmx init ./connector --preset connector --offline .   # host + conn
wasmx init ./main --preset main --offline .             # host + resx + msgx + userx
wasmx init ./full --preset full --offline .             # host + all resources

The current release is installed offline from the .tgz files; npm currently provides the host and userx; other resource packs will be available in a later version.

4. List installed resources

wasmx list

This prints each resource name and its wasm/ path.

5. Upgrade

1. Stop the host:

   wasmx stop

2. Replace with the new .tgz from the downloads page:

   wasmx add ./keragi-userx.tgz

3. Start and check:

   wasmx start
   wasmx status

Keep the resource pack compatible with the host version; when upgrading resources, verify the host version too.

6. Remove a resource

There is no automatic remove command yet. You can:

1. Stop the host;
2. Remove the entry from wasmx.json resources;
3. Delete the matching .wasm under wasm/;
4. Start the host again.

7. Next steps

• Configuration: resource prefixes and rate limits.
• Deploy the web client: connect the frontend to the server.