bdukes/powershell-profile

My personal PowerShell profile and custom modules

A PowerShell Profile for Developing and Managing Web Sites on the DNN Platform

This profile includes a number of modules, primarily supporting the "DNNing" module, which is used to create and restore DNN sites, as well as other maintenance tasks, like removing and upgrading the sites.

Getting Started

The following prerequisites are required in order to use this profile:

• You must have relaxed the PowerShell execution policy
  • In an administrative powershell session, run Set-ExecutionPolicy RemoteSigned
• Install the PowerShell Community Extensions
  • Run the installer from Codeplex
  • OR install via Chocolatey
• Install the 7-Zip command-line tool
  • Via Chocolatey
• SQL Server PowerShell Snap-in
  • Install SQL Server Management Server 2012 or later
• (Optional) Install ImageMagick
  • Install from their website
  • Via Chocolatey
• Setup a repository of DNN packages
  • Create an environment variable called soft pointing to the root of this "software repository"
  • Inside this folder, create a folder structure like this, DNN\Versions\DotNetNuke 7, which contains the DNN 7 community platform packages (install, source, upgrade, and symbols)
  • In addition, if you have Evoq packages, add them to DNN\Versions\DotNetNuke PE or DNN\Versions\DotNetNuke EE for Evoq Content or Evoq Content Enterprise, respectively.
  • (I realize that this structure doesn't work for everyone, and I'm open to pull request and suggestions to make it easier)

Once all of that is in place, you can clone this repository into the default PowerShell profile location (so you'll also need git installed). From a PowerShell session:

git clone https://github.com/bdukes/PowerShell-Profile.git $profile\.. --recursive

If you already have a PowerShell profile, you can clone this elsewhere and manually merge it into your existing profile.

powershell-profile's Issues

Replace 7-Zip dependency with PSCX's Expand-Archive

PSCX (already a dependency) has an Expand-Archive cmdlet, which works for 7z and zip and a bunch of other formats.

Use URL extension when watermarking logos

Instead of always watermarking with "DEV," try extracting the URL's extension, so that "mysite.local" is watermarked with "LOCAL"

Don't require passing version for source when restoring site

When restoring a site, allow passing includeSource flag, without specifying the specific version. In that case, inspect DotNetNuke.DLL in the extracted website to get the version.

Warn/error if required environment variables aren't set

The script uses some environment variables for paths and other info. It should warn if they aren't set (and probably offer to set them)

Progress

Use powershell-style progress to indicate how many steps are in the process

Allow specifying webroot file path

Instead of hard-coding C:\inetpub\wwwroot, use an environment variable(?)

Support restoring from folder, not just zip

If the site backup is a folder instead of a zip, just copy from it.

Create "Getting Started" section in Readme

Change includeSource switch

Having a switch parameter that defaults to $true is weird (to not include source, you need to pass -includeSource:$false). This parameter should be switched to be the negative, so it can default to $false, and be turned on just by the presence of the switch (e.g. New-DNNSite siteName -withoutSource)

Setup SSL certificate & binding

If a site being restored has SSL setup, create a local, self-signed SSL cert and assign it to the site in IIS (currently all SSL is disabled, instead)

Provide a way to install Evoq

Right now, the New-DNNSite command always grabs the community package. You should be able to point it to another type of package, but if there was a simpler mechanism for specifying which sort of package to install, that'd be good.

Robots.txt

Add noindex/nofollow directive

Install pre-defined list of DNN modules, providers, etc.

Install the DNN Dummy Caching Provider to catch serialization issues.

Create database schema if it doesn't exist

If New-DnnSite is passed a $databaseOwner, it should create that schema (right now, it assumes that if it is passed in, it's part of a restored database)

Allow specifying SQL server info

Don't always assume its the local default instance

Setup all portal aliases

If restoring a site, update the portal aliases to something local (e.g. dnnsoftware.com becomes dnnsoftware.com.dev), and setup host file entries for them, as well as IIS bindings.

Watermark favicons during restore

Just like the logo, the favicon should get some kind of watermark

Support <location>

When something in the web.config that the script updates is in a <location> element, the script fails to update it.

Remove-DNNSite should remove HOSTS entry

Remove site from HOSTS file