Speed up the site and make it more readable.
- Use Orchard 1.9 instead of Orchard 1.8.
- Use Sql Azure instead of Sql Compact.
- Use a larger font, calmer background color, and simpler layout.
- Keep the existing simplicity and print layout.
First, export content from the existing site, using the Import/Export module. We did this in segments.
E.g. First, export the Blog.
- Blog Archive
- Blog Post
On each export, we also included:
- Only Published Versions
- Site settings
- Create a
stagingdeployment slot in MS Azure.
- Create a
- Connect the
stagingdeployment slot to the
- Download the Orchard Source (31 MB) into local Git staging branch.
- Create a custom deploy.cmd script for
- Add, commit, and push the
- Force add the media/Media source files (because our global .gitignore ignores Media directories.)
git add **/src/**/[Mm]edia/* -f
- After Git Deploy has finished (about 30-minutes the first time), navigate to
domain-staging.azurewebsites.net, which will show the Orchard Setup page.
- Create a new SQL Azure database.
- Link the database to the Web App.
- Continue thru Orchard Setup
- Use the new SQL Server database.
- Choose the Blog recipe.
- When setup completes, go to the Dashboard > Modules > Import/Export > Enable.
- Once enabled, import each
export.xmlfile that we created in the first step.
- We did the imports with the Orchard command line interface.
- It's also possible from the web user interface, though we needed to increase the
executionTimeoutin the web.config.
- Our import took about 5-minutes.
- Finally, copy across the Media directory from
- Replace the /lib directory with a Nuget packages.config file. Alternatively, can we just delete the /lib directory and have Nuget work anyway? I.e. read the *.sln file?
- Speed up the deployment.
- Remove modules we aren't using, so the Azure Web App doesn't need to build them.
- Create multiple deploy.cmd scripts, for different scenarios (e.g. just deploy static files with no build.)