rig.yaml reference

rig.yaml lives at the project root. The CLI accepts a single application or an apps map. Camel-case field names are canonical; documented snake-case aliases remain accepted by the parser.

workspace:
  deployment: { strategy: incremental }
name: web
port: 3000
install: npm ci
start: npm start
health: { path: /healthz }
visibility: public

Reference	Fields
Application	Identity, process, health, routes, volumes, CLI executables
Workspace	Image, resource defaults, shared environment, shared volumes
Source and dependencies	Local paths, Git source, app dependencies, cache declarations
Configuration	Environment, secrets, generated credentials, parameters
Deployment strategy	Incremental versus image selection and restrictions

For a multi-app project, put local app fields under each name-keyed entry with path. A published ref entry selects a recipe instead of local source; path and ref are mutually exclusive. Do not mix root start/port with apps. See local deployment for a workflow rather than field lookup. This reference targets v0.13; deployment strategies explains changed deployment behavior.

Start here

Deploy applications

Configure applications

Workspaces and storage

AI and tools

Operate and troubleshoot

Examples

CLI reference

Build on Rigbox