Remote Targets

The CLI and Terminal use different Forge addresses:

Client

Address

Purpose

aurum CLI

user@host[:port]

SSH source transfer and remote CLI execution.

Terminal

https://host/api/v1

Browser-visible REST and WebSocket access.

Register a CLI remote

aurum remote add prod aurum@forge.example.com --default
aurum remote add staging aurum@staging.example.com:9022

Remote names use lowercase letters, digits, and hyphens, beginning with a letter.

aurum remote list
aurum remote show prod
aurum remote remove staging

SSH requirements

  • the host accepts key-based SSH authentication;

  • the remote account has aurum on PATH;

  • the local key is available through the normal SSH configuration;

  • non-standard ports are included in the registered URL;

  • host-key verification succeeds before an unattended deployment.

Test the same route independently when delivery fails:

ssh aurum@forge.example.com aurum status

CLI routing

Commands that expose --server can target a named remote:

aurum list --server prod
aurum status signal-watch --server prod
aurum logs signal-watch --server prod --tail
aurum stop signal-watch --server prod --wait

The default remote only removes the need to name the target during push. For lifecycle commands, prefer an explicit --server in automation.

Continue with Forge Connections to register the public API address in Terminal.