Delivery
Delivery is where your organization’s sites are set up, and where changes to your configuration go live. It has two screens:
- Delivery › Delivery › Sites lists every site your organization runs: the domain it answers on, whether it is active, how many browser origins it accepts and how many products cover it. Open a site to change its settings and issue its API keys. See Sites.
- Delivery › Deployments › Versions is your organization’s deployment log. A deployment is one numbered entry in that log: the configuration that was live from that moment. See Versions.
Draft and deployed configuration
Section titled “Draft and deployed configuration”What you edit in the console is the draft. Requests are decided against the deployed document: the configuration in your newest deployment. A change to a site, a product or a feature therefore reaches requests after the next deploy, not when you save it. A few settings take effect at once instead, and their pages say so: a site’s API keys and the transactional mail settings are two.
There is no rollback. To undo a change, you change the draft back and deploy again, which adds a new entry to the log. See Stage and deploy a change and Undo a change.
Where requests arrive
Section titled “Where requests arrive”Your sites call EdgeKit on your tenant host, written your-tenant-host in these docs. Browser-facing paths are also
served under /edgekit/ for organizations that forward /edgekit/* from their own domain. Some paths take a
different credential under /edgekit/: see
Is /edgekit/v1/… the same API as /v1/…?. A request
for one site names it with the x-edgekit-site-id header. See
Select a site on a request.
Isolation
Section titled “Isolation”Each organization has its own database and its own sign-in instance, and shares neither with any other organization. A site id can only ever select one of your own organization’s sites.