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 to move changes between environments. This follows a left-to-right deployment approach. Changes start in the local or left-most environment and are deployed to the production/Live environment. This workflow is called the mainline.
The mainline environments are used when building and deploying the initial website. Upgrades, both manual and automatic also go through the mainline environments.
Flexible environments can be used to work on features separate from the mainline. This is done without interfering with upgrades or other changes being worked on in the mainline.
Umbraco Cloud separates schema and content during deployment. Schema includes Document Types, Templates, Forms, Views, and config files. Content includes content items and media.
Deploy: Moves schema between environments using a Git client or the Umbraco Cloud Portal.
Transfer: Move content and media directly via the Umbraco backoffice.
Schema is stored in a Git repository. These are deployed between environments using a Git client or the Umbraco Cloud Portal.
Content and Media items are not stored in the Git repository. They must be transferred directly from the Umbraco backoffice using the Queue for Transfer option. Once queued, use the Deployment Dashboard in the Content section to complete the transfer.
Content editors do not need Umbraco Cloud Portal access. They can manage content through the backoffice, while developers handle schema deployments via Git.
The source and target environments must be in sync before transferring content and media. Deploy schema 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.
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
Schema 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.
