Summary
Running orx up ties the dashboard server to the terminal session. When the SSH connection drops or the terminal is closed, the server dies. There is also no clean way to stop a running orx up instance without knowing its PID.
Desired behaviour
orx up -d / --detach — starts the dashboard server in the background as a detached process, redirects stdio to a log file, verifies health, then exits immediately so the terminal/SSH session can be closed freely.orx down — stops any running orx up instance regardless of how it was started. Discovers the target via the local pidfile, health endpoint probe, or process table scan; shuts down gracefully via /api/down, escalating to SIGTERM/SIGKILL if needed. Supports --remote <HOST> for remote delegation.
Summary
Running
orx upties the dashboard server to the terminal session. When the SSH connection drops or the terminal is closed, the server dies. There is also no clean way to stop a runningorx upinstance without knowing its PID.Desired behaviour
orx up -d / --detach— starts the dashboard server in the background as a detached process, redirects stdio to a log file, verifies health, then exits immediately so the terminal/SSH session can be closed freely.orx down— stops any runningorx upinstance regardless of how it was started. Discovers the target via the local pidfile, health endpoint probe, or process table scan; shuts down gracefully via/api/down, escalating to SIGTERM/SIGKILL if needed. Supports--remote <HOST>for remote delegation.