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

Non-Interactive Installation

Use the installer JSON and dry-run boundaries for automation without exposing secrets or assuming success.

Automation should use an explicit configuration path, --json, and a preflight gate. Secrets remain in the operator’s secret system; they are not placed in public examples or command arguments.

Code
node "$INSTALLER_DIR/dist/index.js" install --config "$CONFIG_FILE" --dry-run --json

The current CLI reports a validated workflow and preserves an operator-approval boundary for mutation. Treat exit code 2, blocked checks, malformed JSON, or missing expected manifest fields as a failed automation step.

Verification

Capture the redacted JSON result, command exit code, source revision, and release package identity. Then perform the same post-install acceptance checks as an interactive installation.

Related articles

PreflightRun and interpret the source-verified AutoCore installer preflight before mutation.Installation ManifestUnderstand the installer and edition manifests used to identify source, configuration, files, and compatibility.Installation VerificationVerify process, container, migration, dependency, routing, and application readiness after AutoCore installation.