1. Home
  2. Docs
  3. Platform administration
  4. Filesystems and public media
Platform administration

Filesystems and public media

Separate private operational files from public CMS assets and keep generated artefacts durable.

Developer v2026.10 Updated 9 Nov 2026

Disk roles

Operational uploads and exports should remain private by default. Public website or brand media may use a public disk. Keep the distinction explicit in environment configuration.

Container deployments

A local filesystem inside an ephemeral container is not durable unless the target path is mounted to persistent storage. Verify directory ownership and write permissions before enabling uploads, exports, or presentation generation.

Object storage

Use S3-compatible storage when multiple app instances need the same files, when host replacement must not lose data, or when the volume of exports/media makes local disks operationally risky.

Was this page helpful?

Still stuck?

Open a ticket and reference this page — we will pick it up from there.

Open a ticket