Deploy on a VPS

This guide covers deploying a Kyushu worker on a fresh VPS. The example uses Hetzner Cloud with Ubuntu 24.04, but any VPS with a recent Ubuntu/Debian works.

Prerequisites

A VPS with Ubuntu 24.04
A domain pointing to the VPS IP (A record)
SSH access as root

Setup

Update the system and install Caddy

apt update && apt upgrade -y
apt install -y curl caddy

Install the Kyushu CLI

curl -fsSL https://kyushu.dev/install | bash
source $HOME/.cargo/env
kyu --version

Deploy your worker

Copy your built artifacts to the VPS — the kyushu.run.toml, the compiled wasm, and any static files:
Terminal window
```
mkdir -p /opt/yourwebsite
rsync -av ./dist user@yourserver:/opt/yourwebsite/ # For example
```

Create a systemd service

cat > /etc/systemd/system/kyushu.service << 'EOF'
[Unit]
Description=Your Site
After=network.target

[Service]
ExecStart=/root/.cargo/bin/kyu run kyushu.run.toml
WorkingDirectory=/opt/yourwebsite
Restart=on-failure
RestartSec=5

[Install]
WantedBy=multi-user.target
EOF

systemctl daemon-reload
systemctl enable kyushu
systemctl start kyushu
systemctl status kyushu

The service starts automatically on boot and restarts on failure.

Configure Caddy

Once your domain’s DNS has propagated, configure Caddy as a reverse proxy. Check propagation first:
Terminal window
```
dig yourdomain.com +short @8.8.8.8
```
Then write the Caddyfile:
Terminal window
```
cat > /etc/caddy/Caddyfile << 'EOF'
yourdomain.com {
    reverse_proxy localhost:5987
}
EOF

systemctl restart caddy
```
Caddy automatically provisions and renews a TLS certificate via Let’s Encrypt.

Verify

curl https://yourdomain.com

Updating

To deploy a new release, stop the service, replace the files, and restart:

systemctl stop kyushu
# copy your updated artifacts to /opt/yourwebsite
systemctl start kyushu