These are the commands that need no ids: run them inside a directory you have deployed from, or point them anywhere with -app NAME.

​
uncloud deploy

Package the current directory and ship it. The first run creates the app; later runs reuse .uncloud/config.json, so you pass nothing.
The directory is tarred excluding .git, node_modules, and .uncloud, then uploaded to the builder. After submitting, the command watches the build and prints new log lines until it finishes or you press Ctrl+C.

​
Monorepos

List your apps once at the repo root, one path per line:
.uncloud-apps
Each path is deployed in turn. Builds are submitted without watching — check any one with uncloud -app NAME status. uncloud-apps.json works too, as {"apps": ["apps/api", "apps/web"]}.

​
uncloud status

Watch the linked app: replica readiness, the current deployment, build status, new build-log lines, and recent events. Refreshes every 3 seconds until Ctrl+C.
status runs until interrupted, which is wrong for a script or an agent. Use uncloud apps status APP_ID for a single non-blocking reading.

​
uncloud redeploy

Roll out the current spec without rebuilding — the way to apply an env or image change.

​
uncloud logs

Container logs, unwrapped from their JSON envelope so they pipe like any other log stream.

​
uncloud env

Read and write the app’s environment. With no arguments it prints the current values, one KEY=value per line.
Changes merge into the existing environment rather than replacing it, and are saved immediately. They reach the running container on the next uncloud redeploy, which the command reminds you to run.
env prints secrets in plain text, because that is what it is for. Be careful where you run it — CI logs and shared terminals keep scrollback.

​
uncloud scale

Set the replica count and roll it out in one step.

​
uncloud open

Print the app’s public URL and open it in your browser. An internal-only app has no public URL, so it prints its in-cluster endpoint instead.

​
uncloud domain

Manage the hostnames an app answers on. See Domains and TLS for the full flow, including the DNS record.

​
uncloud db

Provision a database for the linked app and print its credentials in .env form. See Databases.

​
Working from anywhere

Every command above takes -app, so none of them actually require the directory: