Installation

runy is one binary. It holds the CLI, the daemon and the web console. Install it with the script or download it.

Install script

curl -fsSL https://setup.runy.dev | sh

The script detects your platform, downloads the matching binary from runy.dev, checks its sha256 and puts runy in ~/.local/bin (RUNY_INSTALL_DIR changes that). Pass a version to install one in particular: curl -fsSL https://setup.runy.dev | sh -s 0.6.0.

Download

Download the binary for your platform and put it on your PATH:

curl -fsSL -o runy https://runy.dev/cli/latest/runy-darwin-aarch64
chmod +x runy && mv runy ~/.local/bin/

Binaries exist for darwin-aarch64, darwin-x86_64, linux-x86_64 and linux-aarch64 (the Linux ones are static), each with a .sha256 next to it. Every version stays available under https://runy.dev/cli/<version>/.

Check the install:

runy --version

watchman

runy follows your resource files, and the file sets of watch and watcher, through watchman. Install it for the workspace to pick up edits as you save them:

brew install watchman

Without watchman everything still works: the daemon reads the resource files once when a workspace starts and again on runy signal workspace restart, and watch and watcher resources stay idle.

Ports

The daemon listens on two addresses. The API and the console are on 127.0.0.1:4122 (--port on every command). The web proxy for port domains is on 0.0.0.0:80 and answers loopback clients only. If something else holds port 80 the daemon says so in runy ns and carries on without the proxy; runy daemon start --proxy-addr 127.0.0.1:8080 moves it.

Note

macOS refuses an unprivileged bind below 1024 on 127.0.0.1 but allows it on the wildcard address, which is why the default is 0.0.0.0:80. Connections from other machines get 403 and are closed.

Next

Getting started writes a first workspace.