ownstack deploy
Synopsis
ownstack deploy [APP] [--stack=NAME] [--wait] [--image [TAG]]
| Command | What it does |
|---|
ownstack deploy | Deploy the linked app to all its stacks. |
ownstack deploy my-app | Deploy a specific app. |
ownstack deploy --stack=prod-east | Deploy only to one stack. |
ownstack deploy --image | Image deploy (default tag from registry config). |
ownstack deploy --image=ghcr.io/me/app:v1.2.3 | Image deploy with explicit tag. |
ownstack deploy --wait | Stream the build log live. |
Inspecting deployments
$ ownstack remote deploy-log [--app=NAME] [--deployment=ID] [--follow]
How it works
- CLI hands the (app, optional stack, optional image) to the control plane API.
- Control plane enqueues one deployment job per target stack.
- Each job SSHes to its stack, pushes your repo (or pulls the image), runs build + release + restart.
Common pitfalls
| Symptom | Cause |
|---|
A deploy is already in progress | An earlier deploy hasn't finished. Wait, or check the dashboard for stuck jobs. |
No git repository | App's git_repository_url is unset. Set it in the dashboard or via API. |
| Build succeeds, healthcheck fails | Web process not bound to $PORT. See Healthchecks. |
Read next