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

Interactive Installation

Understand the verified installer command boundary and the operator decisions required for an interactive run.

The current commercial installer package exposes an install command that runs the source-verified preflight, acquires the installer lock, and emits a manifest-shaped result. The application setup itself is completed through the API installation contract after infrastructure and migrations are ready.

Safe sequence

  1. Verify the authorized release package and configuration.
  2. Run preflight and resolve blockers.
  3. Confirm the target installation and backup boundary.
  4. Run the reviewed install command.
  5. Complete the API setup flow for the first administrator and primary market.
  6. Verify status, health, migrations, application surfaces, and the manifest.
Code
node "$INSTALLER_DIR/dist/index.js" install --config "$CONFIG_FILE"

The command is guarded by a concurrency lock. The operation is not a license to skip database, proxy, or external-service verification.

Verification

Confirm the command result, migration state, setup response, and post-install acceptance record before declaring the installation complete.

Related articles

PreflightRun and interpret the source-verified AutoCore installer preflight before mutation.First AdministratorCreate or confirm the first AutoCore administrator through the source-verified installation setup contract.Primary Market SetupConfigure and verify one installation-scoped primary market for AutoCore Commercial 1.0 RC.