rig deploy

Deploy the project from its rig.yaml

Usage: rigbox deploy [OPTIONS]

Options:
      --from-dir <FROM_DIR>
          Project directory containing rig.yaml. Defaults to cwd
          
          [aliases: --from]

      --output <OUTPUT>
          Output format [default: human, or `rig config set output …`]
          
          [possible values: human, json, yaml, text, table]

      --query <JMESPATH>
          Filter output with a JMESPath expression

  -w, --workspace <WORKSPACE>
          Target workspace (name or id). When unset, reuses the single workspace bound in .rig.lock, or spawns a fresh one

      --cli-input-json <FILE>
          Read inputs from a JSON file or '-' (stdin)

  -n, --name <NAME>
          Workspace name when spawning a new workspace

      --app <APP>
          Deploy only the named app (multi-app projects)

      --cli-input-yaml <FILE>
          Read inputs from a YAML file or '-' (stdin)

      --generate-cli-skeleton
          Print a fillable input template, then exit

      --watch
          Re-deploy on source changes (single-app projects only)

      --no-pager
          Do not pipe help output through a pager

      --prune-stale
          Drop .rig.lock bindings to workspaces that no longer exist, then exit without deploying

      --stage <STAGE>
          Deployment stage. Also loads `.env.<stage>` and `.env.<stage>.local` (precedence: real env > .env.<stage>.local > .env.local > .env.<stage> > .env). Falls back to $RIG_ENV

  -v, --verbose
          Verbose diagnostics on stderr: per-phase deploy tracing, job-poll status, and transport commands. Useful for debugging a slow or stuck `rig deploy`

      --no-env-file
          Skip auto-loading `.env` / `.env.<stage>` files

      --reimage
          Allow re-imaging a pre-existing workspace from a frozen image, discarding its current filesystem. Required to deploy a `reproducible: true` app into a workspace that wasn't created by this deploy and isn't already image-pinned

      --build-only
          Build/publish the frozen image(s) for `reproducible: true` apps and stop — no workspace, re-image, or rsync. A later `rig deploy` reuses the image

      --sync-only
          Sync every app's files but skip the restart pass — stage code without interrupting the running services

      --strategy <STRATEGY>
          Deploy managed app releases or explicitly build a workspace image
          
          [possible values: incremental, image]

      --deployment-id <DEPLOYMENT_ID>
          Stable deployment attempt ID for retries (incremental releases only)

      --bluegreen <BLUEGREEN>
          Stage a change before swinging production traffic at it; pair with `--promote` to swap atomically (zero-downtime). `<suffix>` stages an sibling app at `<base>-<suffix>` on its own subdomain. The special value `preview` instead clones the WHOLE workspace into a hidden preview (every app), overlays your new code, and serves it at `<app>-pv-<id>.rigbox.dev` — `--promote` then re-homes prod onto it.
          
          Pick by what the workspace IS: `preview` is for production SERVICE hosts (it swaps to a new workspace, so the old one is retired — open SSH sessions in it don't follow the swap). For a workspace people actively work IN (SSH, shells, dev processes), deploy in place or use `<suffix>` (same workspace, ~1s app restart) so sessions and workspace state survive.

      --promote
          After staging via `--bluegreen <suffix>`, swap the production subdomain to the staged sibling in one atomic DB transaction (zero-downtime). The previous production app is retained as a rollback target until you delete it.
          
          Requires `--bluegreen`.

  -h, --help
          Print help (see a summary with '-h')

Deploy the project from its rig.yaml

Usage: rigbox deploy [OPTIONS]

Options:
      --from-dir <FROM_DIR>
          Project directory containing rig.yaml. Defaults to cwd
          
          [aliases: --from]

      --output <OUTPUT>
          Output format [default: human, or `rig config set output …`]
          
          [possible values: human, json, yaml, text, table]

      --query <JMESPATH>
          Filter output with a JMESPath expression

  -w, --workspace <WORKSPACE>
          Target workspace (name or id). When unset, reuses the single workspace bound in .rig.lock, or spawns a fresh one

  -n, --name <NAME>
          Workspace name when spawning a new workspace

      --no-pager
          Do not pipe help output through a pager

      --app <APP>
          Deploy only the named app (multi-app projects)

  -v, --verbose
          Verbose diagnostics on stderr (per-phase deploy tracing, job-poll status)

      --watch
          Re-deploy on source changes (single-app projects only)

      --prune-stale
          Drop .rig.lock bindings to workspaces that no longer exist, then exit without deploying

      --stage <STAGE>
          Deployment stage. Also loads `.env.<stage>` and `.env.<stage>.local` (precedence: real env > .env.<stage>.local > .env.local > .env.<stage> > .env). Falls back to $RIG_ENV

      --no-env-file
          Skip auto-loading `.env` / `.env.<stage>` files

      --reimage
          Allow re-imaging a pre-existing workspace from a frozen image, discarding its current filesystem. Required to deploy a `reproducible: true` app into a workspace that wasn't created by this deploy and isn't already image-pinned

      --build-only
          Build/publish the frozen image(s) for `reproducible: true` apps and stop — no workspace, re-image, or rsync. A later `rig deploy` reuses the image

      --sync-only
          Sync every app's files but skip the restart pass — stage code without interrupting the running services

      --strategy <STRATEGY>
          Deploy managed app releases or explicitly build a workspace image
          
          [possible values: incremental, image]

      --deployment-id <DEPLOYMENT_ID>
          Stable deployment attempt ID for retries (incremental releases only)

      --bluegreen <BLUEGREEN>
          Stage a change before swinging production traffic at it; pair with `--promote` to swap atomically (zero-downtime). `<suffix>` stages an sibling app at `<base>-<suffix>` on its own subdomain. The special value `preview` instead clones the WHOLE workspace into a hidden preview (every app), overlays your new code, and serves it at `<app>-pv-<id>.rigbox.dev` — `--promote` then re-homes prod onto it.
          
          Pick by what the workspace IS: `preview` is for production SERVICE hosts (it swaps to a new workspace, so the old one is retired — open SSH sessions in it don't follow the swap). For a workspace people actively work IN (SSH, shells, dev processes), deploy in place or use `<suffix>` (same workspace, ~1s app restart) so sessions and workspace state survive.

      --promote
          After staging via `--bluegreen <suffix>`, swap the production subdomain to the staged sibling in one atomic DB transaction (zero-downtime). The previous production app is retained as a rollback target until you delete it.
          
          Requires `--bluegreen`.

  -h, --help
          Print help (see a summary with '-h')