1.0.0-rc.1 · Release Candidate1 min read
Configuration Overview
Understand the boundary between installer configuration, runtime environment, installation records, and external services.
AutoCore configuration has four distinct layers:
| Layer | Authority | Typical consequence |
|---|---|---|
| Installer file | configSchemaVersion, edition, operator metadata, safety defaults | Preflight and installer workflow |
| Runtime environment | API URLs, database, Redis, Meilisearch, mail, storage, payment references | Process boot and provider readiness |
| Installation record | edition, initialized state, primary market, locale, currency, timezone, distance unit | Database-backed setup and request behavior |
| Edition profile | brand, bundled locale, namespace, feature and provider boundaries | Build and deployment identity |
There is no implicit edition. Unset or unknown AUTOCORE_EDITION fails fast. Secret values belong in an external secret mechanism and are never displayed by the reference.
Verification
For every change, identify the owning layer, whether a restart or migration is required, the backup gate, and the verification command or endpoint. Do not treat a changed environment value as proof that persisted installation state changed.
Related articles
Environment VariablesSource-verified runtime environment keys grouped by database, application, storage, mail, and provider concerns.Configuration FileReference the verified flat installer configuration file and its safe public examples.Configuration BoundariesSee which AutoCore decisions belong to the platform, edition, installation, market, or external provider.