Manage an application
Open an application from Applications to inspect its configuration, deployments, endpoints and resource history. Check the workspace, project and application name before changing a running workload.
Find the right view
| View | What it is for |
|---|---|
| Overview | Source, commands, capacity, public and private endpoints |
| Deployments | Release history and build output |
| Analytics | Resource and available HTTP traffic history |
| Logs | Runtime standard output and errors |
| Terminal | An explicitly connected, privileged container shell |
| Domains | Custom hostname verification and routing |
| Settings | Description, source/build, resources and runtime data |
Use Open application when a public endpoint exists. Workers and private services are verified through logs, their callers and appropriate service checks.
Save settings by section
| Section | Effect of saving |
|---|---|
| General | Updates the description; does not deploy |
| Source and build | Starts a deployment with the selected source/build configuration |
| Resources | Starts a deployment with the selected pool and application limits |
| Runtime data | Starts a deployment with environment, volume and networking settings |
Save one coherent change at a time. Other unsaved sections remain drafts. Use a section’s reset action to discard its edits; navigation warns about unsaved changes.
Configuration can save successfully while its deployment fails. Follow the warning to deployment output and correct the saved configuration. Do not assume the form is still unsaved, or create a duplicate application.
Handle saved secrets
Saved environment values are not returned to the browser. Keep a saved value unchanged or enter a replacement. You cannot reveal the original value; the reveal control shows only a new value you entered. A renamed variable needs a replacement value. See Build and runtime configuration.
Update or recover a release
Save a source, resource or runtime section to deploy its new configuration, then inspect Deployments, Logs and a safe application check. The current dashboard has no standalone restart, redeploy or one-click rollback action. To return to a known release, select its source version or image tag and save the relevant configuration through a new deployment.
Image tags can move; keep your own known-good release references. A deployment history entry is not an automatic data-restoration mechanism.
Move to a different pool
Confirm the destination is active, writable and has enough capacity. Remove custom domains before changing the pool. Plan data transfer and backups; changing the pool does not establish that persistent data has moved. Private service placement, IP addresses and externally published ports may also change.
Delete an application
With project write permission, open Settings → Delete application. Review the named application’s impact, type its exact name and select Delete application.
Deletion removes its containers, public routes, generated DNS and deployment history. Named volumes and shared build caches remain on the server. The pool and optional hosted charges remain unchanged. DNS records you created at your own provider need separate cleanup.
A failed cleanup retains the record and deletion intent for retry. Deployments and settings changes are restricted while deletion is pending. Inspect the error and retry cleanup rather than assuming the resource is gone.