Installation

Install the rdc CLI on your workstation. This is the only tool you need to install manually — everything else is handled automatically when you set up remote machines.

Linux and macOS

Run the install script:

curl -fsSL https://get.rediacc.com | sh

This downloads the rdc binary to $HOME/.local/bin/. Make sure this directory is in your PATH:

export PATH="$HOME/.local/bin:$PATH"

Add this line to your shell profile (~/.bashrc, ~/.zshrc, etc.) to make it permanent.

Windows

Run the install script in PowerShell:

irm https://www.rediacc.com/install.ps1 | iex

This downloads the rdc.exe binary to %LOCALAPPDATA%\rediacc\bin\. Make sure this directory is in your PATH. The installer will prompt you to add it if it is not already present.

Verify Installation

rdc --version

You should see the installed version number.

Updating

To update rdc to the latest version:

rdc update

To check for updates without installing:

rdc update --check-only

To rollback to the previous version after an update:

rdc update rollback

Remote Binary Updates

When you run commands against a remote machine, the CLI automatically provisions the matching renet binary. If the binary is updated, the route server (rediacc-router) is restarted automatically so it picks up the new version.

The restart is transparent and causes no downtime:

• The route server restarts in ~1–2 seconds.
• During that window, Traefik continues serving traffic using its last known routing configuration. No routes are dropped.
• Traefik picks up the new configuration on its next poll cycle (within 5 seconds).
• Existing client connections (HTTP, TCP, UDP) are not affected. The route server is a configuration provider — it is not in the data path. Traefik handles all traffic directly.
• Your application containers are not touched — only the system-level route server process is restarted.

To skip the automatic restart, pass --skip-router-restart to any command, or set the RDC_SKIP_ROUTER_RESTART=1 environment variable.