Social

Search Results

It has been a while since I wrote about the Moriyama runtime for Umbraco - and that is because it has undergone quite a bit of development.
I want to talk about the concept of a Deployment Adapter - that hooks into Umbraco publish and unpublish events to add and remove content to a runtime.
The serialisation of content has already taken place. The deployment adapter is simply responsible for sending that content somewhere:
The definition of a deployment adapter looks like this:
using... action);
}
}
At Moriyama we have several implementations:
FTP
Azure Blob storage
Amazon S3
GIT
REST
ZIP
We'll take a look at the last one. The REST deployment adapter sends the serialised content to an endpoint and allows the receiving

If you use Octopus deploy to deploy your Umbraco sites, you've probably forgotten to increment the Client Dependency version before building and deploying - which leads to old CSS and JavaScript being served.
Octopus Deploy allows you to run custom powershell scripts during the deployment life cycle - and the one below will set the client dependency version.
$Config = ".\config\ClientDependency.config";
If (Test-Path $Config) {
$Cd = New-Object System.Xml.XmlDocument
$Cd.Load($Config...['Octopus.Release.Number'])" | Out-File "bin\version.txt"
The script should be run post deployment. Rather than incrementing the client dependency version - it derives an integer from the octopus release version, so the client dependency version is distinct for each

This post is highly subjective.
My web CMS architecture separates into 3 circles, Content Management Deployment and Runtime.
The three should be able to operate entirely independently of one another though in an ideal world the Runtime...)
Obviously – I am simplifying here. Some CMS may also have some kind of workflow component that defines a process for publishing content.
Deployment
So with the key point of this post being that the three circles should be able to operate entirely independently of one another it follows that they must communicate in some way.
The job of the deployment circle is: To provide the latest version of all content to the runtime(s).
I’d say the best way to achieve this is to have your CMS output

software comes with a fully templated "sample
web site" and sample workflows, which work
out-of-the-box.I agree with Tom about the example workflows. They cover some
sample scenarios for content publishing/deployment and I have often
used them