An App runs project code as a service. This focused guide covers an existing, configured App; creating a host, assigning secrets and configuring units are separate operator decisions. A Job Run or Release publication does not deploy an App automatically.
Inspect the target and select a source
Starting from scratch? Deploy Node with PostgreSQL walks through host selection, unit setup and a first deployment.
rp app list
rp app show <app>
Check the App's host, units, source setting and intended environment with the project's operator. For a reproducible manual deploy, use an approved full commit SHA. Avoid treating a branch label as evidence of what bytes were deployed.
Deploy and verify
rp app deploy <app> --sha <full-sha>
rp app info <app>
rp app logs <app> --tail 100
Deployment can fail; check the App's reported state, unit health and logs, then verify the running service at its expected address. Do not declare success merely because a command started a build. If a production service is unhealthy, follow the project's incident and rollback procedure rather than assuming a new deploy is harmless. A task preview is a separate temporary App with its own URL and limits; it is not this production deployment.