Deploy the web client

The web client is a prebuilt static frontend with no source code. It connects to the server through config.json at the site root.

1. Get the static package

Download keragi-app-web.tar.gz from the downloads page.

After extracting:

dist/                 # static frontend build
config.example.json   # configuration template
README.md

2. Host dist/

Serve dist/ from any static server. Because the frontend uses client-side routing, configure SPA fallback: unmatched paths should fall back to index.html.

The hosting root should be dist/, so these paths resolve:

• /index.html
• /assets/*
• /resource/*

3. Configure service addresses

Copy the template:

cp config.example.json dist/config.json

Edit dist/config.json:

{
  "meta": { "version": "0.1.0", "mode": "private" },
  "services": {
    "userx": "https://your-host/userx",
    "msgx": "https://your-host/msgx",
    "agix": "https://your-host/agix",
    "conn": "https://your-host/conn"
  },
  "capabilities": { "connector": true }
}

• If the frontend and server are same-origin, use relative paths: /userx, /msgx, /agix, /conn.
• If they are different origins, use a reverse proxy for those paths to the wasmx host to avoid cross-origin configuration.
• If the connector or AI engine is not installed, conn / agix can be null.

Reload the page after editing.

4. Verify

1. Open the web client.
2. Check the browser console for failed resource loads or API 404s.
3. Sign up / sign in and confirm userx is reachable.
4. Send a message and confirm msgx works.
5. If agix / conn are installed, verify those features too.

5. Client platforms

The web client is available now. Desktop (Linux / Windows / macOS) and Android clients are coming soon.

Next steps

• Configuration: server prefixes and ports.
• WASM resource packs: selective installation.