Deploy a Project

This workflow starts with a reachable Forge environment and a local Aurum project whose aurum_project declaration contains a new version.

Register the target

aurum remote add prod aurum@forge.example.com --default
aurum remote show prod

Use the SSH username, host, and port provided by the Forge administrator. Key authentication must work without an interactive password prompt.

Push the version

From any directory, pass the project path and remote name explicitly:

aurum push ./signal-watch prod

push:

  1. reads NAME and VERSION from aurum_project;

  2. rejects the operation if that version already exists;

  3. packages the project source without local build output;

  4. transfers the package over SSH;

  5. compiles and registers the version on Forge.

A published name@version is immutable. Update the version in CMakeLists.txt before pushing a new release.

Start and verify

aurum run signal-watch \
  --server prod \
  --version 0.0.1 \
  --wait

aurum status signal-watch --server prod
aurum logs signal-watch --server prod --tail

For a live venue account, add the credential reference expected by the Forge environment:

aurum run signal-watch --server prod --version 0.0.1 --auth okx-live

Credential material must already exist in the target’s secret store. push does not include local secrets.

Rollback

Stop the current version and start a previously registered version:

aurum stop signal-watch --server prod --version 0.0.2 --wait
aurum run signal-watch --server prod --version 0.0.1 --wait

Check Terminal after each transition; desired state, process state, runtime health, and data freshness are separate signals.