Skip to content
mcorucu docs
AutoCore1.0.0-rc.1 · Release Candidate
1.0.0-rc.1 · Release Candidate1 min read

Installation Verification

Verify process, container, migration, dependency, routing, and application readiness after AutoCore installation.

HTTP 200 is not sufficient verification. Acceptance must distinguish:

  1. The process exists and the container is healthy.
  2. PostgreSQL migrations are aligned with the application image.
  3. Redis and Meilisearch dependencies are reachable with the intended namespaces.
  4. Web, admin, API, and worker surfaces are the intended applications.
  5. The reverse proxy routes each surface correctly.
  6. A fresh worker or proxy process sees the current configuration.
  7. Installation status is initialized and data-preservation checks pass.

The rehearsal suite verifies health, public and admin pages, API installation status, proxy configuration, service restart, installer status/doctor, backup verification, and rollback planning in disposable environments.

Verification

Record each check as pass, warning, or blocked. Preserve the source revision and manifest identity with the acceptance record.

Related articles

Installation ManifestUnderstand the installer and edition manifests used to identify source, configuration, files, and compatibility.Doctor and StatusUse the installer status and doctor commands to distinguish installation state from full service health.Failure and Degraded ModesSee how AutoCore represents delayed search, media failure, worker gating, provider failure, and partial readiness.