1.0.0-rc.1 ยท Release Candidate2 min read
Configuration File
Reference the verified flat installer configuration file and its safe public examples.
The installer accepts a JSON file or a flat YAML file selected with --config. The public sanitized examples use these nine keys:
| Key | Type | Required by the parser | Source-backed behavior |
|---|---|---|---|
configSchemaVersion | number | No; defaults to 1 for the preflight check | Only version 1 passes preflight. |
edition | string | No in the parser, but required in practice | Must be autocore or eskisehiraraba. |
environment | string | No | Retained as operator metadata in examples. |
domain | string | No | Retained as operator metadata; real domains stay external. |
locale | string | No | Example market metadata. |
currency | string | No | Example market metadata. |
timezone | string | No | Example market metadata. |
paymentEnabled | boolean | No | true blocks installer preflight. |
backupDirectory | string | No | Used as the displayed preflight backup directory. |
The parser is intentionally small: it is not the API setup schema. The API setup contract is documented in the first administrator and primary market setup pages.
Verification
Run the installer with an explicit config path and --json. Confirm the returned status and checks before an install or upgrade command.
Code
node "$INSTALLER_DIR/dist/index.js" preflight --config "$CONFIG_FILE" --json
Related articles
Configuration OverviewUnderstand the boundary between installer configuration, runtime environment, installation records, and external services.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.