- Download the AppData/Sites, Media, Modules, and Themes/<any-in-use-themes> folders from the existing v1.7 site.
- Download a new Orchard.Web.1.8 site. Delete its AppData and Media folders.
- Copy and paste content into the new site:
- The AppData/Sites and Media folders.
- All in-use themes from the Themes folder (ignoring built in themes).
- Package the existing Theme; import it into the new site.
Note: these instructions do NOT yet cover module migration. Basically, list all the modules & features that the existing site uses. Then make sure those are installed & enabled on the new site.
I have an existing Orchard CMS hosted in a Windows Azure Website. I would like to upgrade to v1.8. Here are the steps. Note: Works on my machine!
We should not deploy an Orchard CMS from source control. There are two reasons. First, doing so would overwrite the AppData, Media, Modules, and Themes folders on each push. We don’t want that. Those folders hold end-user data. Second, we don’t need source control for a deployment of Orchard. We aren’t modifying its source! We only modify the source to create themes and modules.
We should deploy Orchard with Visual Studio/WebMatrix/WebDeploy/FTP/Etc, and then we should regularly backup the site.
- WebMatrix to download the existing site from Azure.
- Visual Studio to publish the new site to Azure.
- Command Prompt to package the existing theme.
- Windows File Explorer to copy and paste the AppData and Media folders.
Download the current Orchard CMS assets from Azure.
WebMatrix is the alternative when FTP isn’t working.
- Login to Windows Azure Portal
- Open your site
- Click the WebMatrix button
- Choose “Edit local copy”
- Choose, “No, just download the files and database”
- The files will land in \Documents\My Web Sites\TheSiteName
In the case that FTP is working, download just these folders:
Usually, I store the download in my Downloads folder.
Gather the current site’s assets into one folder.
- Create a new folder to hold the assets. (This folder will act as a backup and migration package.)
- Copy and paste the following into that folder:
- Nuget package of the current theme.
Here is how to create the Nuget Package.
Orchard.exe package create MyThemeName c:\temp
Create a new, local Orchard CMS v1.8.
There are many ways to obtain a local copy. Here are three:
- Create it from Windows Azure Gallery. Then download it with WebMatrix.
- Create it from WebMatrix (File > New > Site from Application Gallery).
- Download Orchard.Web.1.8.zip from orchard.codeplex. Unblock before unzipping.
- For the remaining steps, I work almost entirely out of the Downloads folder.
Note: We use Orchard.Web because we do not need to modify the source.
Copy, paste, and import the current into the new.
- Copy the entire App_Data folder
- Copy the entire Media folder
- Run the new site locally (do NOT run Orchard setup), to import the theme and module packages.
- I run the site via IISExpress through Visual Studio or WebMatrix
- A better way might involve the Orchard command line. For now, I am get ACL problems that way.
Publish the new to the current Azure Website.
- Do this with Visual Studio or WebMatrix.
- More details coming soon.
- Once that’s done, it’s okay to ZIP and/or delete the local copies of both the new and the old Orchard CMS.
- http://www.slopeofkongwahill.com/ on 22 May 2014 to upgrade from v1.7 to 1.8
- More coming soon.
Bugs along the Way
- Orchard.Web.1.8 doesn’t build in Visual Studio 2013.
- package install Orchard.Theme.PackageName C:\temp\PackageName.nupkg doesn’t work.
- Can I do all of the above with Visual Studio and not WebMatrix?
- When we use Git Deploy, how does Windows Azure choose the csproj to run?
- Can I automate much of this with PowerShell?
- Download file from web.
- Unblock and unzip to specific location.
- Move folders.
- Import theme.