Skip to main content
Start with your first app. Rigbox runs applications inside workspaces: deploying application code and replacing a workspace image are different operations. An incremental release prepares code separately, then activates and verifies the affected apps. It retains workspace identity and development files. Activation can briefly interrupt an app. Store mutable data outside the managed code directories, preferably on persistent volumes.

Select a strategy

For predictable local and CI behavior, declare workspace.deployment.strategy: incremental or image in rig.yaml. CLI flags override that declaration. Without either, the CLI chooses image deployment when any app has reproducible: true, and incremental otherwise. Catalog-only and legacy preview flows have separate compatibility paths; use their dedicated guides. The console retains its reviewed repository strategy. A manifest declaration must match it; editing the file alone does not approve a console strategy change.

Organize a project

Use one manifest for multiple cooperating apps, declare dependencies, or deploy one app. Keep configuration in the manifest and credentials out of source control.

Operate a release

Develop and redeploy, stage before activation, and restore app code and configuration. Use image release history only for workspace images.