Deployment lifecycle

Appaloft models deployment as detect -> plan -> execute -> verify -> rollback.

This lifecycle explains user-visible deployment state. Users need to know which step failed, which input it used, and how to recover.

Detect

Detect reads source and configuration evidence to identify application type, build behavior, runtime entrypoint, and network exposure.

Common failures:

Source cannot be read.
Repository ref or base directory does not exist.
App type cannot be detected and no runtime profile was supplied.

Plan

Plan turns source, runtime, health, and network configuration into an executable plan that explains what Appaloft will run.

The plan should summarize build, start, health check, and access routing decisions.

Execute

Execute builds, uploads, starts, and routes the application in the selected target environment.

Execution failures often involve network, credentials, image pulls, build commands, server resources, or runtime backend behavior. Inspect logs and diagnostics before changing domains.

Verify

Verify checks process state, health policy, proxy routing, and access URLs.

Verify failure does not always mean the process failed to start. It may be health path, listener port, proxy routing, or access URL observation.

Rollback

Rollback is the recovery path after failure. It should not hide failure as success.

How to read status

Start from the latest failed phase:

detect failed: fix source or configuration.
plan failed: fix resource profiles.
execute failed: inspect server, credentials, build, and runtime logs.
verify failed: inspect health, network, proxy, and access route.
rollback failed: manual intervention is required; save diagnostics first.

Related pages: Deployment sources, Logs and health, and Safe recovery.

Deployment status response example:

{
  "id": "dep_123",
  "resourceId": "res_web",
  "status": "verifying",
  "currentPhase": "verify",
  "sourceSummary": {
    "kind": "git-repository",
    "gitRef": "main",
    "baseDirectory": "."
  },
  "recoveryHint": "Inspect health summary before retrying."
}