|Important: The Unity Cloud Content Delivery documentation has moved to docs.unity.com. Please visit the new site for the most up to date information about Unity CCD.|
Cloud Content Delivery (CCD) is a managed cloud service that hosts and delivers content to your application’s users worldwide without having to reinstall a new version of the application. The service is fully integrated into the Unity development platform, saving you months of building and maintaining your own similar service. CCD is most valuable for content-rich, live games or applications that require content updates on a regular basis.
In CCD, you organize your content into buckets to create a clear workflow for your project. A typical workflow example could be having separate buckets per platform (for example, an iOS bucket and an Android bucket). Within a given bucket, you group specific versions of each asset to create a release. As these versions change, or you add and remove entries, you designate new releases as required.
A release can also have a unique identifier associated with it, called a badge. Give this badge a meaningful name, then use it to query content, and move it between releases to add flexibility to your workflow.
Using Cloud Content Delivery, you organize your content into buckets to create a clear workflow for your project. A bucket is a single context for publishing content, such as the platform or environment. A typical workflow example could be having separate buckets for development, staging and production builds, with names such as
A. The details of a bucket as it appears in CCD, including bucket ID and description.
B. The details for a release within that bucket.
An entry is a single unit of content within a bucket. Entries support labels and metadata. Creating a release captures the current state of all the entries in the bucket, similar to a versioning process.
A. The details of the currently selected release.
B. An asset within this release, and its details.
The simplest way to push files into your bucket is to use the CLI’s
sync command. This pushes a local folder’s contents to the remote bucket, which automatically adds, updates and deletes contents in the bucket, as necessary.
When you create a release, CCD takes a snapshot of all the entries (at their current versions) contained in a bucket at that specific point in time. To remove, update, or add entries, you must create a new release in order to deliver the new or changed entries.
Badges enable you to select which release your application uses. You can assign a unique badge to a release, and request that content using that badge’s name.
A. A row showing a release in a bucket’s Releases tab.
B. The badges, if any, associated with this release.
You can move this badge between releases, adding more flexibility to content workflows. Moving a badge removes it from the previous release that it was associated with. You can only assign a badge to a single release at a time, but you can associate multiple badges to a release.
By default, an automatically generated badge named
latest is assigned to the latest release.