Saved the settings, headed over to the deployment history and forced a redeploy of my last commit.Īnd sure enough, it was running as expected. The debugging still happens like it always has, with the node V8 debugger, except Visual Studio connects to the debugger over another socket (remember, you can even debug node.js remotely running on a Linux or Mac like this) and translates how V8 thinks into how Visual Studio thinks about debugging. The key needs to be Project, and the value has to be. The most flexible way of doing so is an app setting entry in the Azure Management Portal itself, under the Configure tab of your website. The second last paragraph on this Kudu help site brought me on the right track, as well as a comment on the first tutorial mentioned above: it is necessary to tell Azure website to look one level deeper. It just didn’t tell me, as deployment history showed green. Which means, Azure will get confused about the nature of your project (won’t recognize it as node.js application) and fail more or less miserably. sln file lives, the project is one level deeper. Contrary to the tutorial I followed yesterday, my “real code” does not live in the root of my git repo. However, for some reason the project template uses a Guess its path? Right, bin/Problem 2Īre we good now? Not quite. gitignore file, which excludes everything beneath bin folders. gitignore file. This seems to be a variation of the standard Visual Studio. After yesterday’s experience, I figured it would work in about 30 seconds. For a difference overview of these project types, check out the “Converting to an Azure project type” section on their deployment wiki page.Īfter the project wizard did it’s job, I created a new commit, created an azure website, added its git endpoint as remote, and pushed. I was not using any of the Azure variants listed here, as I did not need the deployment scripts they add in this case. So after installing I created a blank Node.js app. This give me a lot of benefit out of the box that I’m not even going to mention here, but Scott Hanselman was pretty excited about it some time ago. I am usually working with Visual Studio, so I wanted Node.js Tools for Visual Studio. On a personal note, I’d like to add that publishing to Azure Websites using git (and getting this really useful deployment history) is something that makes me happy on every single deployment. Much to my surprise, I did in just six minutes.
I figured I’d never make it on first attempt.
Yesterday, I was trying to deploy a node.js application with express.js to an Azure Website. I was following this tutorial.
0 kommentar(er)
