Create the release, "live", and the instance, "home".
"home" refers to the component of the
mirios project that we will be deploying (there are other projects in the build output). The source directory
is the location that the build process places the 'naked' build.
Click 'deploy' on dashy client, to push the build into source control
Go over to dashy server (on my webserver) and create the mirios project
The "base repo path" refers to the publically-available source control server where we just committed to
As this server will be handling the 'live' deployment, we create that, and the instance
Settings "0" for the refresh period means it will only update when we click "force update".
Now we need to edit the 'deployment actions' for this specific configuration (live -> home), so I click that
And set the 'deploy directory', where dashy server will perform the 'update' into
Then we set up the directory that dashy will copy the files across to
It's nice to set it up this way
because SVN's hidden folders mess with IIS, and it means we can make changes to this directory without
upsetting SVN
Now we quickly check to show that the mirios website currently has nothing on it, and it is so.
So, we click "force update", and watch it go through the steps
Then we check to see if it works ...
It does! Success!
Rollback
Below is a video demonstrating how the 'rollback' process works. I demonstrate it against this very website itself:
The steps are like so:
This is the (now old) dashy website
Let us go to the dashy server website and click 'rollback' and specify a revision number
Lets wait
Dashy server says that it is complete, lets go and check
It's loading slowly
Lets go back to dashy server and see what it says. It says all is completed
Lets check for ourselves ... Indeed!
This is the old website
Okay, let us go and force an update again, to get back to the latest