CDN and content
Public files
Files use a UUID and become public only through an authorized host.
#Overview
Files use a UUID and become public only through an authorized host.
#From upload to delivery
A file belongs to the organization and, when specified, to a zone. Upload supports TTL, a direct public link, and selected storage nodes. Details show UUID, name, size, public path or URL, and replication status.
Public delivery requires a proxied file host and stored allowed-host metadata at the edge. An object can be stored while not yet publicly ready.
#Publish a file
Choose the zone and a readable regular file.
Set TTL and direct-link behavior for the use case.
Wait for required replicas to become available.
Test the public URL and retain the UUID for API or CLI operations.
#State lifecycle
| State | Meaning |
|---|---|
active | Logical object active and distributed to selected nodes. |
purged | Content removed from caches; object may remain referenced depending on the action. |
archived | Object retained outside active delivery. |
#Verifiable example
cdn-pizza upload -z ZONE_ID -f ./dist/app.css --cache-ttl 86400
cdn-pizza files -z ZONE_ID --json