Another Way To Deny Verbs in IIS

I recently needed to deny the TRACE verb to all incoming requests to IIS on a website running as a classic cloud service in Azure. First I tried following this post and adding the following: <system.webServer> <validation validateIntegratedModeConfiguration=”false” /> <modules runAllManagedModulesForAllRequests=”true” /> <handlers> <add name=”DenyOTH” verb=”OPTIONS,TRACE,HEAD” path=”*” type=”System.Web.HttpMethodNotAllowedHandler” /> </handlers> < [Read More]

Continuous Deployment Of Ghost On Azure

Here's how I got Ghost running on Azure from my own GitHub repo with a custom theme. First, shout out to Steven Niemitz for his BlogML2Ghost solution which allowed me to port my BlogEngine.Net instance to Ghost. Once I knew that I could port all the content, I deployed Ghost on Azure by creating a new app service and walking through the UI steps to create a new Ghost [Read More]

GHOST_NODE_VERSION_CHECK and Windows

I was trying to get Ghost running on my local Windows box and everything was going great until I got the following error: ERROR: Unsupported version of Node Ghost supports LTS Node versions: ^4.2.0 || ^6.9.0 You are currently using version: 7.7.2 This check can be overridden, see http://support.ghost.org/supported-node-versions/ for more info So, basically, I'm running a version of Node greater [Read More]

Passing An Azure Staging Slot URI To A Test Runner In Visual Studio Team Services Release Management

I wanted to run our coded ui tests using Selenium against the staging uri during our continuous integration workflow of our cloud service web role. But the problem arose that I didn’t know the dynamically generated URI that gets created by Azure when deploying to the staging slot. I chatted with DevOps guru Thiago Almeida about this and he had the following suggestion: Add a Powershell script between the [Read More]