Skip to content

Deployment results and proof

Use the deployment reference returned by Forge to inspect the selected commit and deployment outcome. Follow Deploy to retrieve the URL when the application is serving.

Inspect the result

Replace DEPLOYMENT_REF with the returned reference:

aegis forge status DEPLOYMENT_REF --json

The response includes application_url when the deployment is serving. The field can be absent or null when no current URL is available. Human-readable status also displays the URL after deployment succeeds and its route is ready.

Keep useful diagnostics

Retain these non-secret facts when investigating a deployment:

  • The GitHub origin and selected commit, ref, or repository.
  • The manifest and relevant source changes.
  • The local HTTP result and deployed application's response.
  • The deployment reference, result, and failure stage when present.

These records describe one deployment. A ready route and an observed response do not establish long-term availability or authorize another operation.

Investigate a failure

Inspect the source selection first, then the manifest and build output. For a runtime failure, inspect startup, port binding, and readiness. For a missing URL, read the deployment and route status before retrying.

See Troubleshooting for failure categories and Support for the information to include in a report.

Historical qualification records

The Aegis 0.9 journey retains dated installation, Nexus, deployment, and rollback observations. Its package and application identities describe that audit, not your application.