Deployment
A deployment model that relies on Git, Kudu, and Umbraco Deploy core technology to move your changes from one environment to another.
Last updated
Was this helpful?
A deployment model that relies on Git, Kudu, and Umbraco Deploy core technology to move your changes from one environment to another.
Last updated
Was this helpful?
Umbraco Cloud uses a deployment model based on Git, Kudu, and Umbraco Deploy core technology to move changes between environments. This follows a "left to right" model. Changes start in the local or left-most environment and are deployed to the production environment.
Umbraco Cloud separates metadata and content during deployment. Metadata includes Document Types, Templates, Forms, Views, and config files. Content includes content items and media.
Key Terms:
Deploy: Moves metadata between environments using a Git client or the Umbraco Cloud Portal.
Transfer: Moves content and media directly via the Umbraco backoffice.
Deployment Types:
Metadata Deployment: Metadata, including Document Types, Templates, Forms, Views, and config files, is stored in a Git repository. These are deployed between environments using a Git client or the Umbraco Cloud Portal.
Content and Media Transfer: Content and Media items are not stored in the Git repository. Instead, they must be transferred directly from the Umbraco backoffice using the Queue for Transfer option. Once all required items are queued, the Deployment Dashboard in the Content section is used to complete the transfer.
Content editors do not need Umbraco Cloud Portal access. They can manage content through the backoffice, while developers handle metadata deployments via Git.
The source and target environments must be in sync before transferring content and media. Deploy metadata first to ensure consistency.
Content and media move between environments through the Umbraco backoffice. Content can be transferred from Local to Development and restored from Live or Staging.
The transfer and restore process is the same for Local to Cloud and between Cloud environments.
All configuration for Umbraco Deploy is stored in the appSettings.json file found at the root of your Umbraco website.
Some deployments can trigger an Umbraco Cloud environment to restart. The table below outlines which actions initiate a restart.
Config file change
Yes
Metadata deployment
No
File change (for example, CSS file)
No
Content or Media transfer
No
From the Umbraco Cloud Portal, you can manually restart your environments.
The umbraco-cloud.json file defines deployment settings, identifies the current environment, and determines the next deployment target.
The name attribute in the umbraco-cloud.json can be updated to clarify deployment destinations in the Workspaces dashboard.
Umbraco HQ offers a training course covering best practices for developing with Umbraco Cloud. The course targets frontend and backend developers who currently work or plan to work with Umbraco Cloud.
Explore the Umbraco Cloud Developer Training Course to learn more about the topics covered and how they can enhance your Umbraco development skills.