Deploy Status
Version: {{vm.dashboard.version}}
Status: {{vm.dashboard.status.message}}
Operation time: {{vm.dashboard.status.formattedDateTime}}

Deploy Operations

{{vm.operationMessage}}


Configuration Details

The current environment's configuration is as follows. Updates should be applied to the UmbracoDeploy.Settings.config file.

Setting Options Current Value(s) Notes
Excluded Entity Types <settings> <excludedEntityTypes> <add type="[entity-type]" /> </excludedEntityTypes> </settings>
{{entityType}}

Optionally entity types can be excluded from deployment operations.

Read more

Ignore Broken Dependencies Behaviour <settings> <deploy ignoreBrokenDependencies="true|false" ignoreBrokenDependenciesBehavior="None|Transfer|Restore|All" /> </settings> {{vm.configurationDetails.ignoreBrokenDependencies}}
{{vm.configurationDetails.ignoreBrokenDependenciesBehavior}}

When restoring or transferring content, Umbraco Deploy will make checks to ensure that any dependent content, media or other items are either present in the target environment, or can be deployed from the source environment.

For example, if you have a media picker on a content item, that references a media item that's been deleted or is in the recycle bin, you'll get an error and the deploy won't complete until the issue is resolved (by removing the reference to the deleted media item).

You can configure deploy to ignore these issues and proceed with the transfer operation without warning, by amending this setting.

Read more

Timeout Settings <settings> <deploy sessionTimeout="[timeout in seconds]" sourceDeployTimeout="[timeout in seconds]" httpClientTimeout="[timeout in seconds]" databaseCommandTimeout="[timeout in seconds]" /> </settings> {{vm.configurationDetails.sessionTimeout}}
{{vm.configurationDetails.sourceDeployTimeout}}
{{vm.configurationDetails.httpClientTimeout}}
{{vm.configurationDetails.databaseCommandTimeout}}

Umbraco Deploy has a few built-in timeouts, which on larger sites might need to be modified.

Read more

Transfer Forms Behaviour <settings> <forms transferFormsAsContent="true|false" /> </settings> {{vm.configurationDetails.transferFormsAsContent}}

Forms can be transferred as schema (i.e. serialized to .uda files on disk) or as content via the backoffice.

Read more

Transfer Dictionary Items Behaviour <settings> <dictionary transferDictionaryAsContent="true|false" /> </settings> {{vm.configurationDetails.transferDictionaryAsContent}}

Dictionary items can be transferred as schema (i.e. serialized to .uda files on disk) or as content via the backoffice.

Read more

Transfer Members Behaviour <settings> <deploy exportMemberGroups="true|false" /> </settings> {{vm.configurationDetails.exportMemberGroups}}

By default, member groups are transferred as schema items unless they are disabled via this configuration.

Read more

<settings> <members allowMembersDeploymentOperations="None|Restore|Transfer|All" transferMemberGroupsAsContent="true|false" /> </settings> {{vm.configurationDetails.allowMembersDeploymentOperations}}
{{vm.configurationDetails.transferMemberGroupsAsContent}}

Members, and optionally also member groups, can be transferred via the backoffice if the feature is enabled using these settings.

Read more

Domains Deployment <settings> <content allowDomainsDeploymentOperations="None|Culture|AbsolutePath|Hostname|All" /> </settings> {{vm.configurationDetails.allowDomainsDeploymentOperations}}

When restoring or transferring content for culture invariant content, the information managed under "Culture & Hostnames" can be transferred between environments using Umbraco Deploy.

To enable this, set the configuration value as appropriate for the types of domains you want to allow:

  • Culture - selected culture for the content
  • AbsolutePath - values defined under "Domains" with an absolute path, e.g. "/en"
  • Hostname - values defined under "Domains" with a full host name, e.g. "en.mysite.com"

Combinations of settings can be applied, e.g. Hostname,AbsolutePath

Memory Cache Reload <settings> <deploy reloadMemoryCacheFollowingDiskReadOperation="true|false" /> </settings> {{vm.configurationDetails.reloadMemoryCacheFollowingDiskReadOperation}}

Some customers have reported sporadic issues with Umbraco's memory cache following deploy operations where schema information in Umbraco is updated from the serialized .uda files.

These can be resolved manually by reloading the memory cache via the Settings > Published Status > Caches dashboard.

This configuration option can be used to enable an automated reload of this cache.


Schema Comparison

The following table shows the schema information managed by Umbraco Deploy. A comparison between the information held in Umbraco and that in the .uda files found on disk (in /data/revision) is shown.

If any differences exist, a Schema Deployment From Data Files (to update Umbraco) or an Extract Schema To Data Files (to update the .uda files) operation can be triggered to align the information.

{{entityType}} - {{vm.getSchemaComparisonSummary(comparisonData)}}

Name File Exists In Umbraco File Exists Is Up To Date
{{item.label}} {{(item.filename)}} View Details
Umbraco Deploy is not licensed.