pier_
Reference

pier deploy

Build and roll changed apps and sites (implies apply)

pier deploy [<ref>] [flags]

Build and roll changed apps and sites (implies apply).

Arguments

ArgumentRequiredDescription
<ref>noDeploy one app or site only (name or name/target); default: everything changed

Flags

FlagValueDefaultDescription
-y, --yesSkip confirmation prompt
-f, --forceForce rebuild all apps
--taglatestImage tag
--no-resumeRefuse to resume suspended targets — fail fast (CI escape hatch)
--prune-externalAlso delete resources on the server that aren't in pier.yaml and were never applied from it (added via console/API)
--purgeDeletes in this deploy skip the 30-day recovery window (torn down immediately)
--renameKIND.OLD=NEW,...Apply a rename in place instead of delete+create (KIND.OLD=NEW, e.g. apps.api=gateway). Repeatable.
--pathSTRINGSite only: directory to build and upload (default: the site's build context)
--build-cmdSTRINGSite only: override the build command (build-time only)
--output-dirSTRINGSite only: override the output directory (build-time only)
--skip-buildSite only: skip install and build, upload the directory as is

Global flags apply to every command.

Examples

pier deploy                 # everything changed in the current environment
pier deploy api/stage       # one target
pier deploy -e prod -y      # non-interactive, explicit environment
pier deploy www --path ./dist --skip-build

Behaviour

  • deploy runs apply first. A change that only touches config (variables, plan) is applied and does not roll the workload; a change to the image, build context or a linked secret does.
  • A paused target is resumed before it is rolled unless --no-resume is set.
  • --purge and --prune-external delete; both are refused without -y when there is no terminal.

See also

pier apply · pier deploys · pier rollback · Concepts: apply, deploy, staged

On this page