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 the active workspace:

press deploys list

Output shows each deploy’s ID, slug, type, title, and creation time.

View a deploy

Get details about a specific deploy:

press deploys get 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

Create a URL deploy when the Press.js document is already hosted:

press deploys create \
  --slug hosted-report \
  --name "Hosted Report" \
  --type url \
  --target-url https://app.example.com/report

URL deploys are rendered directly from the configured target URL and do not store deploy versions. See URL Deploys for the full hosted-target workflow.

Update a deploy

Change a deploy’s name or target URL:

press deploys update dep_abc123 --name "Updated Name"

press deploys update dep_abc123 --target-url https://app.example.com/report-v2

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

Managed deploys store an immutable history of versions. Every press deploy creates a new version.

List versions:

press deploys versions dep_abc123

URL deploys return an empty version list.

Aliases

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

press deploys alias dep_abc123 production v_def456

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

Aliases apply to managed deploys. URL deploys render the configured target URL using the latest pointer.

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.