Product concepts
Read desired state first
Most mutations are asynchronous. Understanding desired versus active state prevents an accepted API request or queued operation from being mistaken for a runtime deployment acknowledgement.
Read these short concept guides before changing production state:
- CDN fundamentals explains DNS, TLS, edges, origins, caching, placement, and the limits of a CDN.
- How CDNFoundry works follows one domain from desired state through activation and customer traffic.
- Desired state explains PostgreSQL ownership and derived runtime data.
- Domains and DNS explains lifecycle, delegation, records, and proxy publication.
- Edges and cells explains pools, cells, placement, and isolation.
- Revisions and operations explains asynchronous work, acknowledgement, retry, and rollback.
The common rule is simple: a request validates and commits desired state; a bounded worker later reconciles that state to an external runtime. Serving traffic never waits for Laravel and never passes through it.
New operators should read the pages in the order shown above, then use Using CDNFoundry as the task map.