Use the signed stable CLI 0.13.1 or later and a server with app-release support. See installation requirements and verify
rig --version before starting.Prerequisites
Create a Rigbox account, install the CLI, and install Git locally. Run every command below on your local machine.1. Sign in
2. Get the example
rig.yaml declares port 8080, npm ci, npm start, and /healthz. Open that file and make the deployment choice and route explicit:
visibility: public at the top level if you want anyone to open the example URL; otherwise the route stays private.
3. Deploy
From the example directory:.rig.lock. Keep that file locally; do not copy a production binding into an unrelated project.
4. Check the app
<APP_NAME> with the name returned by the list command. Verify live and port_open are true, then open the actual URL returned by Rigbox. A private route may require authentication.
To look around inside the workspace, connect with ssh my-first-app. Signing in and creating the workspace set up SSH access for you.
Deploy a change
Edit the example and runrig deploy again from the same directory. Activation briefly restarts the affected service; it does not replace the workspace filesystem. See the development loop and app rollback.
Troubleshooting
If install or health checking fails, find the release ID withrig app-release ls --workspace my-first-app and read rig app-release logs --workspace my-first-app --release <RELEASE_ID>. Confirm the process listens on port 8080 and /healthz returns success before retrying.
Cleanup
When you no longer need this test environment, inspect its apps and data first, then remove the workspace withrig workspace rm --workspace my-first-app. This removes the workspace; export data you want to retain before cleanup.