Concepts

Publishing

How a version becomes a release on the CDN and how clients find their files.

Publishing turns a version into a release on the CDN. Run it from Versions in the interface, or through the API.

What publishing does

  1. Checks the version. Running external validation first when it is enabled.
  2. Builds the release: processes every file (see Config files), encrypts the files that are marked for it, and prepares bundles.
  3. Creates one manifest per consumer listing the files that consumer should receive.
  4. Uploads everything to the CDN, so clients get the change right away.

A live log shows each step while it runs.

How clients read it

Every project has a CDN URL, shown on the Integration page. A client loads:

<CDN URL>/<version>/manifests/<consumer>

and then the files listed in that manifest. The SDKs do this for you and poll for updates. See Node.js and Unity.

A version that has never been published gives clients nothing. Publish it at least once.

Bundles

A bundle is a named set of files that are delivered together. Which files belong to a bundle is set per version, so a bundle can look different in default and in staging.

Config files

Supported formats, syntax checks, comments and what happens to a file on publish.

Access and roles

Who can do what in a project.