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

Disk and Storage Planning

Plan persistent database, media, backup, and temporary installation storage for AutoCore.

Storage must cover PostgreSQL data, media binaries, installation state, release artifacts, backups, temporary restore verification, and logs. The current source does not enforce a fixed disk minimum.

Authoritative versus derived storage

PostgreSQL contains transactional marketplace state. Media binaries require a provider-specific backup boundary. Meilisearch documents are derived and can be rebuilt from PostgreSQL when the source and reindex path are available. Redis holds transient cache and queue state and is not a substitute for a database backup.

Verification

Check available space before installation and before upgrades. Include the expected database dump, media snapshot, and temporary restore footprint. Treat an insufficient-disk rehearsal finding as a blocker before mutation.

Related articles

System RequirementsSource-verified host, runtime, dependency, network, and operational prerequisites for AutoCore Commercial 1.0 RC.Backup Before UpgradeCreate and verify the authoritative-state backup required before an AutoCore upgrade.Media ConfigurationConfigure local or object-storage media paths, limits, and public URL boundaries without exposing credentials.Backup ConfigurationDefine backup ownership, scope, encryption, retention, and restore verification for AutoCore.