Skip to main content
A host’s settings live in its config file, ~/.config/amika-hostd/config.toml. Setup writes it. This page covers what you can change after that. After you edit the file, apply it:
  • Runtimes, presets, images, sizes and limits: run amika-hostd reload. The daemon keeps running.
  • Anything else, such as transport or snapshot_dir: restart the daemon with amika-hostd down, then amika-hostd up.

Runtimes

A runtime is how a host runs rigs. A host can have more than one. Setup asks about each runtime the machine can run. To change them later, run capabilities update. It installs what the runtime needs, updates the config file, and reloads the daemon:
  • Add --dry-run to see the plan first.
  • It won’t turn off a runtime that still has rigs.
  • amika host list shows each host’s runtimes.

Notes for each runtime

  • smol: smolvm needs resize2fs (from e2fsprogs) for disks under 20 GiB, and /dev/kvm on Linux. Setup warns you if either is missing.
  • lume: see macOS rigs.
  • bare_metal: see Bare-metal rigs.

Sizes and images

The config file sets the host’s rig sizes, and the image each preset starts. Amika gets the sizes from the host, so edit them in the file. Then run amika-hostd reload.
:latest follows each release. To pin a version, use a 12-character commit SHA, such as amika-coder:855d403678d5.
amika-hostd 0.7.0 and later won’t start with the old [preset_images] table. Run amika-hostd config upgrade or amika-hostd setup to convert it.
Keep disk_gib at 20 or more. Below 20, smolvm doesn’t cache the image, so every create downloads it again.

Snapshots on your host

You can snapshot a rig on your host. The snapshot is a .smolmachine file on the host’s disk, and only that host can use it.
  • Only “snapshot and delete” is available. The daemon stops the rig to pack its disks, so Snapshot everything isn’t offered.
  • Default snapshots don’t apply. A host rig starts from its preset image, unless you pick one of the host’s snapshots.
  • Snapshots are large, several gigabytes each. Point snapshot_dir (or AMIKA_HOSTD_SNAPSHOT_DIR) at a disk with space. The default is ~/.local/state/amika-hostd/snapshots.
amika snapshot list --long shows which host each snapshot belongs to.

Listen on a port

By default the daemon connects out to Amika, so the host needs no open port. If you’d rather have Amika connect in, the daemon can listen on a port. You expose that port to the internet over HTTPS yourself, for example with ngrok or Cloudflare Tunnel. Add this line to the config file, above the first [ line:
The daemon listens on 127.0.0.1:3020 by default. To change it, set host and port in the config file, or pass --host and --port to up. Expose the port, then start the daemon:
If the URL changes, run amika-hostd register-url https://<public-url>. A free ngrok URL changes on every restart.
Register a bare HTTPS hostname, such as https://hostd.example.com, with no path or port. Otherwise browser previews won’t work. Creating and managing rigs still works.Browsers and amika rig ssh connect to that URL directly. Don’t limit it to Amika’s IP addresses or put it behind an access gate.