Managing Deploys

Once you’ve deployed a document, use the deploys command to manage your deployments.

All deploys commands support both interactive login and API keys via --token or the PRESS_CLOUD_TOKEN environment variable. See Authentication.

List deploys

See all deploys in your account:

press deploys list

Output shows each deploy’s ID, slug, title, and latest version.

View a deploy

Get details about a specific deploy:

press deploys get --deploy-id dep_abc123

Create a deploy

Create an empty deploy before pushing a version:

press deploys create --slug my-report --name "Q4 Report"

The slug is a human-readable identifier you’ll use when deploying:

press deploy report --slug my-report

Update a deploy

Change a deploy’s name or settings:

press deploys update --deploy-id dep_abc123 --name "Updated Name"

Delete a deploy

Remove a deploy and its associated cloud data:

press deploys delete --deploy-id dep_abc123 --yes

This permanently removes the deploy resource and its associated deploy data.

Versions

Each deploy stores an immutable history of versions. Every press deploy creates a new version.

List versions:

press deploys versions --deploy-id dep_abc123

Aliases

Aliases let you point a stable name (like production or staging) to a specific version.

press deploys alias --deploy-id dep_abc123 --alias production --version-id v_def456

This makes production always resolve to the latest approved version, while you deploy new versions for testing.

Common alias pattern

production  → v3 (stable, live)
staging     → v4 (testing, next release)
preview-42  → v2 (feature branch)

Set aliases during deploy or afterward — they’re pointers that move independently of version history.