Skip to content
Browse documentation

Infrastructure

Upload, deploy, health-check, and roll back

Run an explicit, reviewable release sequence for an already prepared server.

A successful upload or remote command is not proof that a service is healthy. Keep build, upload, deploy, health, and rollback as distinct saved operations, then verify the public service separately.

Define a safe release recipe

LabelKind / policyCommand or pathTimeout
Upload releaseupload / askartifacts/release.zip → uploads/release.zip120 seconds
Activate releasedeploy / ask./automation/activate-release.sh900 seconds
Check healthinspect / allow./automation/check-health.sh60 seconds
Restore releaserollback / ask./automation/restore-release.sh180 seconds

Deploy in order

  1. Prepare and validate the artifact locally. Each SSH target has a configurable upload limit, defaulting to 1,024 MiB for one artifact. Local project Read permission is also required.
  2. Upload to a relative remote path whose existing parent resolves inside the connection root. Vopit streams through SFTP using a temporary file and rename, then reports byte count and SHA-256.
  3. Approve the reviewed deploy recipe or exact agent proposal. The SSH command uses the server user’s real privileges.
  4. Run a separate health operation and inspect its output. Then visit or probe the configured public URL from an appropriate external location.
  5. If a verified release is unhealthy, run the reviewed rollback operation. Clean up or investigate leftovers after a cancelled or failed upload.

Name the real artifact and its destination

The script names and paths in the recipe table are illustrative. Configure scripts already present and reviewed for your project, or implement them for its release process first. Select the actual SSH account and working directory. An upload stages bytes; activation is a separate action.

  1. Inspect the project manifests, release scripts and deployment guidance, or enable project excerpts in Generate with AI. Check the listed sources and assumptions.
  2. Declare the local artifact directory in Settings > Project when uploading an excluded build output. Select the exact built file and an existing remote parent directory.
  3. Create stack-specific activation and health operations. Include a public URL for external verification, and retain the artifact hash or image digest.
  4. Treat rollback and database restore separately. A code rollback is not proof that a migration can be reversed. See Deployment patterns for application services, containers, clusters, static hosting and databases.

All documentation