Installation Isolation
Understand the data, namespace, and service boundaries that keep AutoCore installations separate.
Installation isolation means that one product/data boundary cannot accidentally read or write another boundary’s state. The source validates explicit edition identity and protects namespaces for cookies, cache, search, storage, queues, database resources, and deployment projects.
Isolation responsibilities
| Boundary | What must remain distinct |
|---|---|
| Database | Installation records, users, listings, policies, payments, and audit state |
| Search | Derived indexes and their prefixes |
| Cache and queues | Redis prefixes, queue names, and transient coordination |
| Media | Storage roots, object prefixes, and public delivery context |
| Browser identity | Cookie namespace and refresh-token cookie name |
| Deployment | Service project, ports, URLs, and selected edition |
The isolation contract is fail-fast: an unset or unknown edition must throw, and cross-edition namespace reuse is invalid. Isolation is not created by a logo change and is not a substitute for network, secret, or access-control review.
Scope limitation
This page explains conceptual boundaries only. It does not provide deployment commands, production topology identifiers, or backup/restore procedures.