Remote Deploy

Push agent updates to remote Akshi nodes via SSH.

Prerequisites

• SSH access to the remote node
• Akshi installed on the remote node
• The remote node running with a runtime.toml

Deploy command

akshi deploy --host user@remote-node.example.com

This performs:

1. Copies updated WASM binaries to the remote node.
2. Runs akshi reload on the remote node.
3. Verifies agent status after reload.

Specifying agents

Deploy a specific agent:

akshi deploy --host user@remote-node.example.com --agent log-monitor

Custom paths

If the remote node uses a non-default installation path:

akshi deploy --host user@remote-node.example.com \
  --remote-dir /opt/akshi \
  --remote-config /opt/akshi/runtime.toml

Deploy with configuration

Push configuration changes along with WASM binaries:

akshi deploy --host user@remote-node.example.com --include-config

This copies runtime.toml and restarts the runtime (since config changes require a restart).

SSH key authentication

The deploy command uses your SSH agent or ~/.ssh/config. For CI/CD pipelines, set the key path:

akshi deploy --host user@remote-node.example.com --ssh-key ~/.ssh/deploy_key

Multiple nodes

Deploy to several nodes:

for host in node-a.example.com node-b.example.com; do
  akshi deploy --host "akshi@$host"
done

Rollback

If the new agent fails, restore the previous version:

akshi deploy --host user@remote-node.example.com --rollback

This restores the previous WASM binary from the backup created during deploy.