Introduction
Press.js Cloud CLI (press-cloud-cli) is a native binary that uploads your Press.js document artifacts to Press.js Cloud and manages cloud deployments.
It is written in Rust and distributed as a standalone binary — no Node.js runtime required.
Two ways to use it
Section titled “Two ways to use it”| Approach | How it works | Best for |
|---|---|---|
Embedded via press CLI | press install cloud downloads and upgrades the binary; press uninstall cloud removes it; press deploy, press login, etc. forward to it automatically | Local development, team workflows |
| Standalone binary | Download directly from GitHub releases and invoke press-cloud-cli commands by itself | CI/CD pipelines, automation, environments without Node.js |
Embedded usage
Section titled “Embedded usage”If you already use the press CLI, installing the cloud CLI is a single command:
press install cloudpress loginpress deployThe press CLI handles binary installation, reads your press.toml configuration, runs the build step, and forwards deploy parameters to the cloud binary. You get a unified press experience without managing a second tool.
Standalone usage
Section titled “Standalone usage”The cloud binary works independently for scripted environments:
press-cloud-cli loginpress-cloud-cli deploy --entry my-report --artifact-path ./distKey features
Section titled “Key features”- Flexible authentication — OAuth device flow for local development, API keys for CI/CD and automation
- Content-addressed uploads — SHA-256 deduplication means only new blobs are transferred on subsequent deploys
- Deploy management — create, version, alias, and roll back cloud deploys
- CI/CD ready — static binary with no runtime dependencies, configurable via environment variables
Architecture
Section titled “Architecture”press.toml ──► press build ──► press-cloud-cli upload ──► Press.js Cloud API ──► deployThe press CLI (optional) runs your build and hands the artifact directory to press-cloud-cli, which uploads it to the cloud API and registers a deploy. Subsequent deploys of the same project only transfer changed files.